Using tmux in a system where screen is not available, "bitbake linux-yocto -c menuconfig" fails with the following error: ERROR: No valid terminal found, unable to open devshell
Created attachment 981 [details] Prototype for integration
Merged into master: http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=d61d0a1fc80dff446d2019c0c0553714ac8cf629
Trying to run: tmux att -t devshell-3171 no sessions Above error occurs using Yocto project 1.4 when I try to configure the kernel using this command: bitbake linux-yocto -c menuconfig I have Yocto project 1.3 installed on same machine, different directory, and the kernel configuration works as expected. It appears that something has changed with 1.4. I checked my Ubuntu 12.04 build machine, and it has the latest 'screen' and latest 'tmux' installed. Any other info needed?
Also, I checked and found that I do have the changes Chris commited to the git master branch. So this may be a new problem symptom. I'm using a custom bsp layer for Microchip's dev board based on the RouterStationPro. I'll regress back to the default RouterStationPro core-image-minimal build tonight and see if that works without errors.
Same problem occurs with Yocto 1.4 when building the default core-image-minimal for the routerstationpro. This regression test halts with this error. bitbake core-image-minimal ... ... ... Trying to run: tmux att -t devshell-3171 no sessions
Should we reopen this bug as I am having the same issue while configuring the kernel? It is related with the bug #4439
This problem is serious as it prevents configuring the kernel with Yocto Project 1.4, can someone look at this and propose a workaround I can try?
Reopened. See failed regression test by Steve Scott and independent verification of failure by Eren Turkay.
Steve, I'm marking this one as fixed again since this entry was for the original feature implementation, and we have bug 4439 to cover the failure. I've just found a patch already in master that should address the problem, so if you could have a look at my comment on bug 4439 and test the indicated patch that would be great.