*** 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
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
also, if i use screen directly, e.g. replace byobu-screen with just
screen, it works as expected.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
*** 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
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
also, if i use screen directly, e.g. replace byobu-screen with just
screen, it works as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
Happened to me twice today. Once while in irssi and the second time in
mutt. I have nethack mode on and have for a long time.
From dmesg:
[743662.124228] screen[11639]: segfault at 0 ip 0040af4d sp
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
happens here too
no, it's not nethack-mode
seems to occure to me mostly, when mcabber or the likes as children
crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
** Changed in: eglibc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
** This bug has been marked a duplicate of bug 375625
screen freezes up, turns zombie
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 375625 ***
https://bugs.launchpad.net/bugs/375625
I have experienced both this bug (where the client complains it can't
find the master process anymore) and the bug now marked a duplicate,
#375625 (where the client freezes, but indeed the master process also
I've been having this same issue intermittently, usually appearing when
exiting a full terminal editor like emacs after re-attaching an old
byobu session. I do not have the issue listed in #727741.
A related issue (possibly the root cause) is given in:
I just had this happen to my machine. I was working in mutt (mutt-
patched) version looking at email. The system is Kubuntu running the
latest Natty beta. apt-get update/upgrade was run within the last 12
hours. The machine has 1.5 gig ram, not much running on it at the time.
From dmesg:
Try dpkg -S /usr/bin/screen. If it states diversion by screen-
profiles to: /usr/bin/screen.real, but you don't actually have screen-
profiles installed, you may be experiencing bug #727741 which may have
left you with an old and crashy version of screen.
--
You received this bug notification
I experience this problem often when working with medium to large log
files (200K) The 10.04 servers I'm experienceing this on have never had
screen-profiles installed. This seems like an unnecessary annoyance at
best and a impediment to work at worst. I'll check dmesg going forward
to see if I
In #8, wrote:
I've had this occur a few times recently; I am using the default byobu
profile, on a 64-bit system with 4 GiB of RAM.
Each time the crash has occurred, I'm exiting vim when signed in from SSH,
and the vim/screen session was started from the local desktop.
The following
I'm subscribed to this bug and will continue following this closely.
But I'm marking the task against Byobu as 'invalid', as I haven't been
able to reproduce it there, and it appears that this crash has happened
for some people outside of byobu.
It would be nice to get to the bottom of this ;-)
I have seen this error only once, and I have been using byobu years
(currently running Ubuntu 10.10).
The one time I saw this message I was connecting from Android's
connectbot and was asked if I wanted to start a nested screen session, I
answered no and quickly lost the connection for unrelated
I just saw this error when I wasn't using byobu... just screen.
--
screen unpredictably crashes
https://bugs.launchpad.net/bugs/644825
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
17 matches
Mail list logo
