Fedora/Redhat have adopted a particular fix to cve-2014-7169, commonly known as a part of the shellshock bug, which includes the patches here [1]. As a consequence, terminal spawning is broken for commands like "bitbake virtual/kernel -c menuconfig". The reason is the environment variables exported via poky/meta/classes/terminal.bbclass include names like "BASH_FUNC_xxx()" which bash itself will not interpret. An example offending line in run.do_terminal.<PID> is ... export BASH_FUNC_module()="() { eval `/usr/bin/modulecmd bash $*` \ }" ... Since the bash that is launched in the spawned terminal cannot interpret the offending line, it fails to run. The user is briefly met with a spawned terminal that immediately closes with no indication of the problem. [1] http://www.openwall.com/lists/oss-security/2014/09/25/13
I tried to reproduce this on fedora 20 and whilst I see that bitbake exits early, menuconfig is launched successfully. Did fedora change the bash patchsets they were applying?
FWIW I've figured this out and will send out a patch to fix things shortly.
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=eb2ea6fd2d2dc626ead13de1ec334d4220651612