Hi Vincent,
Vincent Lefevre wrote:
> In the screen source, the error comes from attacher.c:
[...]
> If I understand correctly, the kill() failed, probably because
> the MasterPid process no longer existed.
Yes, I just recently learned that kill with signal 0 is a common way
to check if another process is running and permission-wise killable
(i.e. belongs to the same user if not running under root) but not
killed.
> And I can confirm that the SCREEN process was no longer running.
I read this code the same way. Then again, starting a screen session
and then killing the SCREEN process does not result in this error
message, just in a frozen screen client, even when resizing the window
afterwards.
> So, in short, the master process died. I don't know the reason,
> but it did not leave a core dump. And it doesn't seem to have a
> logging mechanism.
Meh.
I in the meanwhile tried to reproduce your crash by running a screen
session with mutt in the attachment menu for selecting a file and then
wildly resizing the window as fast as I can, but to no avail. Stable
as a rock. :-/
I saw you're using systemd as init system. Any chance that the screen
session has been started under X initially and this X session vanished
about the same time? Happenend to me recently, but IIRC the symtoms
were different, too.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
