[Bug 644825] Re: screen unpredictably crashes
Mark Smith
mark.launchpad at winksmith.com
Fri May 2 04:39:34 UTC 2014
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
screen not freezing up nor turning zombie, but i got the error described
above. it happens reliably. i just manufactured Ubuntu 14.04. when
exiting using ^A^D it does exactly what this bug describes. my screen
is then lost completely (no longer exists), then i get logged out. the
commands i'm running are:
byobu-screen -d -m -L -a -t amp703 -S amp703 -T xterm-color
byobu-screen -d -r amp703
i then type ^A^D it hangs for about 10 seconds. it then returns this:
Error: Cannot find master process to attach to!
my PS1 appears as would normally happen after a command completes, but
then i am logged out immediately through no action of my own complete
with the word "logout" as if the ^D part was interpreted by my shell.
sure enough, if i just type ^A by itself within byobu, after 10s it
drops to my shell with the master process error above.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/644825
Title:
screen unpredictably crashes
Status in 〣 byobu:
Invalid
Status in “eglibc” package in Ubuntu:
Confirmed
Status in “screen” package in Ubuntu:
Incomplete
Bug description:
Recently on a wide range of unconnected servers, I've been noticing
byobu sessions crashing out, with the message "Error: Cannot find
master process to attach to!" appearing on the console/shell. I have
not yet noticed any unifying factors; this happens when logged on to
the physical console as well as over ssh, while the screen is in use
as well as when it has been idle for a long time.
byobu 2.68-0ubuntu1.1 and screen 4.0.3-14ubuntu1 are in use in all the
cases I've seen (i.e. current upgraded Ubuntu 10.04 servers)
{{{
$ screen -ls
There is a screen on:
4384.pts-0.leela (14/09/10 23:55:39) (Dead ???)
Remove dead screens with 'screen -wipe'.
1 Socket in /var/run/screen/S-jim.
}}}
I have never noticed this behaviour before, and I've been using
vanilla screen for a long time; recently I've been switching to byobu
because I find the on-screen info bars to be useful. For this reason
I'm listing this bug against byobu, but I cannot prove that.
Suggestions for increasing debug visibility would be appreciated -- I
don't want to have to run multi-day sessions under strace, but if
that's what it takes I can do that on at least one server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/byobu/+bug/644825/+subscriptions
More information about the foundations-bugs
mailing list