byobu will not start after upgrade: Cannot exec 'motd+shell'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
byobu |
Fix Released
|
Medium
|
Unassigned | ||
byobu (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
After upgrading to 2.78-0ubuntu1~ppa4 byobu immediate exits after starting and emitting the following error:
Cannot exec 'motd+shell': No such file or directory.
This only occurs when 'motd+shell' was the only window currently selected. This can be easily fixed by commenting out or removing the following line in .byobu/windows:
screen -t shell motd+shell
Or by uncommenting or adding a well-formed line to open a second window.
This does not cause a problem for those using a terminal emulator since they are left with a bash shell and can easily edit the file. However, if you have byobu set to launch at login you will immediate be logged out of your tty. Ideally, you would get thrown back to a shell so that you could fix the error.
Changed in byobu: | |
status: | New → Fix Committed |
importance: | Undecided → Low |
importance: | Low → Medium |
status: | Fix Committed → Fix Released |
Changed in byobu: | |
status: | Triaged → In Progress |
Changed in byobu (Ubuntu): | |
status: | New → Fix Committed |
importance: | Undecided → Medium |
Changed in byobu: | |
status: | Fix Committed → Fix Released |
So symlinking motd+shell definitely fixes the issue on upgrade. However it wouldn't fix the following situation:
A user who uses a tty does the following:
1) Makes changes that have the effect of changing the contents of .byobu/windows to something similar to:
# Default windows examples cache/notify- osd.log
#screen -t notify-osd -M tail -f $HOME/.
#screen -t top top
#screen -t web elinks
#screen -t shell motd+shell
screen -t opps does_not_exist
2) User has launch on login check.
3) User logs out.
4) User logs in.
5) User is immediately logged out when does_not_exist fails to exec.
I'm not sure if there is really anything that can be done about this or if it is really a bug. I just thought I should mention it. I've tested this situation on my Ubuntu desktop, and am not sure how it would play out on ubuntu-server yet.