Jens, can you please also attach an Xorg log from the crash? If I understand the original report right, the X session continued otherwise as normal, so I guess the X server didn't crash. It could have run out of memory temporarily, or xscreensaver requested something out of reach, like loads of memory.
Does the timestamp on your log indicate that xscreensaver died just after killing molecule? xscreensaver also has a -sync option to help debug X troubles, although I don't know if it can help here, can you try with that? Tormod On Sat, Mar 14, 2020 at 9:51 PM Jamie Zawinski <j...@jwz.org> wrote: > > As far as I know, an XIO error means the X server dropped the connection to > the xscreensaver client. So either the X server itself crashed, or it decided > to disconnect xscreensaver for some unknown reason. > > If the client had done something wrong, X11-protocol-wise, this would have > been a more verbose "X" error, not an "XIO" error. > > Maybe this is the kernel OOM-killer shooting down random long-running > processes, as it sometimes likes to do? > > "Resource temporarily unavailable" sure sounds like it could be the X11 > server trying to say that it ran out of memory.
