From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Mike Looijmans <mike.looijmans@topic.nl>,
openembedded-core@lists.openembedded.org
Subject: Re: Getting "menuconfig" to work again?
Date: Thu, 31 Dec 2015 11:04:35 -0600 [thread overview]
Message-ID: <56856023.5060407@linux.intel.com> (raw)
In-Reply-To: <5685347E.5080003@topic.nl>
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?
> If I kill that process, the menuconfig magically appears.
>
next prev parent reply other threads:[~2015-12-31 17:00 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 [this message]
2016-01-01 9:18 ` Mike Looijmans
2016-01-01 17:58 ` Paul Eggleton
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=56856023.5060407@linux.intel.com \
--to=leonardo.sandoval.gonzalez@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