Summary: no nethack options active, and "sufficient" memory.
{{{
j...@moonshine:~$ echo $NETHACKOPTIONS
j...@moonshine:~$ ls -l .nethackrc
ls: cannot access .nethackrc: No such file or directory
j...@moonshine:~$ free -m
total used free shared buffers cached
Mem: 2511 2475 35 0 14 2140
-/+ buffers/cache: 320 2191
Swap: 7357 0 7357
}}}
Actually, it seems odd that the screen patch you identified would have
changed a nethack message into a generic message ... it looks more like
a nethack-specific message had been left in attacher.c by accident.
So, looking at screen's attacher.c, it seems as if this message can only
happen if the MasterPid becomes unresponsive (i.e. doesn't respond to a
kill 0), or something to do with AttacherChld happens ...
Now, is there a byobu process that invokes screen? And would that
qualify for control over whatever MasterPid is supposed to be?
--
byobu/screen unpredictably crashes "Cannot find master process to attach to!"
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
