Getting "menuconfig" to work again?
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.
Signature · 1 line
Mike Looijmans
Quoted 7 lines · Mike Looijmans
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:
Quoted 8 lines
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
If I kill that process, the menuconfig magically appears.
Signature · 1 line
Mike Looijmans
Quoted 15 lines · Mike Looijmans
Quoted 14 lines · Mike Looijmans
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"
Quoted 6 lines
Quoted 1 line
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?
Quoted 2 lines
If I kill that process, the menuconfig magically appears.
Quoted 20 lines · Leonardo Sandoval
Quoted 17 lines · Mike Looijmans
Quoted 15 lines · Mike Looijmans
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.
Quoted 7 lines
Quoted 4 lines
Extra info: apparently it spawns a process:
/usr/bin/python3/usr/bin/gnome-terminal--versiongnome-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
Quoted 1 line
Quoted 1 line
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!
Signature · 1 line
Mike Looijmans
Hi Mike,
Quoted 32 lines · On Fri, 01 Jan 2016 10:18:55 Mike Looijmans wrote:
Quoted 18 lines · Leonardo Sandoval
Quoted 17 lines · Mike Looijmans
Quoted 15 lines · Mike Looijmans
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.
Quoted 7 lines
Quoted 3 lines
Extra info: apparently it spawns a process:
/usr/bin/python3/usr/bin/gnome-terminal--versiongnome-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.2Quoted 1 line
Quoted 1 line
If I kill that process, the menuconfig magically appears.
Quoted 8 lines
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.
Quoted 1 line
Happy New Year!
Same to you! :)
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 39 lines · Paul Eggleton
Hi Mike,
Quoted 36 lines · On Fri, 01 Jan 2016 10:18:55 Mike Looijmans wrote:
Quoted 16 lines · Leonardo Sandoval
Quoted 15 lines · Mike Looijmans
Quoted 14 lines · Mike Looijmans
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"Quoted 7 lines
Quoted 4 lines
Quoted 1 line
But nothing happens from that point.
Extra info: apparently it spawns a process:
/usr/bin/python3/usr/bin/gnome-terminal--versiongnome-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.2Quoted 1 line
Quoted 1 line
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".
Mike, this is definitely a bug that you hit. Can you file it in https://bugzilla.yoctoproject.org/?
Quoted 13 lines
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.
Quoted 1 line
Happy New Year!
Same to you! :)
Cheers,
Paul
Quoted 40 lines · Paul Eggleton
Hi Mike,
Quoted 37 lines · On Fri, 01 Jan 2016 10:18:55 Mike Looijmans wrote:
Quoted 18 lines · Leonardo Sandoval
Quoted 17 lines · Mike Looijmans
Quoted 15 lines · Mike Looijmans
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.
Quoted 7 lines
Quoted 3 lines
Extra info: apparently it spawns a process:
/usr/bin/python3/usr/bin/gnome-terminal--versiongnome-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.2Quoted 1 line
Quoted 1 line
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.
Quoted 7 lines
Quoted 3 lines
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.
Nice... For me simply removing the "version" part fixed the problem. A simple "try and ask forgiveness" patch wasn't as simple as I thought, the actual terminal command execution is being done elsewhere.
On newer Ubuntus, the "--version" just hangs, probably waiting for terminal input or something silly like that.
For now, I'd say removing the version check would be better - if you happen to have that bad 3.10 version, you get a nice error message. That's a lot easier to diagnose than a hangup.
Quoted 2 lines
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.
To be quite honest, I don't know what desktop I'm running. I just run whatever was default with Ubuntu, so that might be Gnome...
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: [email protected]
Website: www.topicproducts.com
Please consider the environment before printing this e-mail