From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Getting "menuconfig" to work again?
Date: Sat, 02 Jan 2016 06:58:11 +1300 [thread overview]
Message-ID: <3915097.5a95lnvstk@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <5686447F.60200@topic.nl>
Hi Mike,
On Fri, 01 Jan 2016 10:18:55 Mike Looijmans wrote:
> On 31-12-15 18:04, Leonardo Sandoval wrote:
> > On 12/31/2015 07:58 AM, Mike Looijmans wrote:
> >> On 31-12-15 14:55, Mike Looijmans wrote:
> >>> When running a "menuconfig" (or any other task that needs a terminal),
> >>> bitbake just "stops" and doesn't show any terminal.
> >>>
> >>> I'm using the current master branch of everything, on Ubuntu 15.
> >>>
> >>> When running with "-D" I can see the following log:
> >>>
> >>> DEBUG: Executing task do_menuconfig
> >>> DEBUG: Attempting to spawn terminal "custom"
> >>> DEBUG: No custom terminal (OE_TERMINAL_CUSTOMCMD) set
> >>> DEBUG: Attempting to spawn terminal "tmux-running"
> >>> DEBUG: Attempting to spawn terminal "tmux-new-window"
> >>> DEBUG: Attempting to spawn terminal "gnome"
> >>>
> >>> But nothing happens from that point.
> >>
> >> Extra info: apparently it spawns a process:
> >>
> >> /usr/bin/python3 /usr/bin/gnome-terminal --version
> >
> > gnome-terminal is a pain... there are some checks base on the version
> > and based on that certain parameters are set. which g-t version are you
> > using?
>
> $ gnome-terminal --version
> GNOME Terminal 3.14.2
>
> >> If I kill that process, the menuconfig magically appears.
>
> Digging into the source code, I saw that "gnome-terminal --version" is
> only being called to determine if the "--disable-factory" option should
> be passed to it. For some reason, in OE that call "hangs", I suspect
> because of the way the environment and pipes are laid out at that point.
>
> If I just run 'gnome-terminal -t hello --disable-factory -x sh' I don't
> get any errors and it works just fine. To me it looks like the whole
> version check could be removed and always pass "--disable-factory".
Unfortunately that's what we did earlier and it was fine until gnome-terminal
stopped accepting that option. Perhaps it's now a no-op in the version you're
using, I'm not sure; but in 3.10 they made it trigger an error.
It ought not to be too hard to fix the hanging - hopefully someone with a GNOME
desktop installed (not me) can figure out what's happening there.
> Happy New Year!
Same to you! :)
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2016-01-01 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 13:55 Getting "menuconfig" to work again? Mike Looijmans
2015-12-31 13:58 ` Mike Looijmans
2015-12-31 17:04 ` Leonardo Sandoval
2016-01-01 9:18 ` Mike Looijmans
2016-01-01 17:58 ` Paul Eggleton [this message]
2016-01-07 15:11 ` Leonardo Sandoval
2016-01-08 8:12 ` Mike Looijmans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3915097.5a95lnvstk@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=mike.looijmans@topic.nl \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox