[OE-core] Getting "menuconfig" to work again?

Mike Looijmans mike.looijmans at topic.nl
Fri Jan 1 09:18:55 UTC 2016


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".

Happy New Year!

-- 
Mike Looijmans



More information about the Openembedded-core mailing list