Bug#953098: xscreensaver: Crashes with XIO: fatal IO error
I was running xscreensaver continuously for a couple of months but could not reproduce. If nobody else can reproduce and you cannot provide more information I must at least lower the severity of this bug report. Regards, Tormod On Thu, Mar 26, 2020 at 10:29 PM Tormod Volden wrote: > > Jens, the log indicates the machine has an Intel(R) HD Graphics 530 > (Skylake GT2) GPU. Is this the same for the other machines? I have > been trying to reproduce for several days, also running on Intel > drivers, but with a 5500 series GPU and also I am on "testing" so I > have newer Xorg and kernel. > > Tormod
Bug#953098: xscreensaver: Crashes with XIO: fatal IO error
Jens, the log indicates the machine has an Intel(R) HD Graphics 530 (Skylake GT2) GPU. Is this the same for the other machines? I have been trying to reproduce for several days, also running on Intel drivers, but with a 5500 series GPU and also I am on "testing" so I have newer Xorg and kernel. Tormod
Bug#953098: xscreensaver: Crashes with XIO: fatal IO error
For best logging: xscreensaver -verbose -log log.txt
Bug#953098: xscreensaver: Crashes with XIO: fatal IO error
Hi, sorry for the late answer but we're currently mostly shutdown because of COVID-19 and other things took priority. On 14.03.20 21:41, Jamie Zawinski wrote: > Maybe this is the kernel OOM-killer shooting down random long-running processes, as it sometimes likes to do? No, if that were the case, we'd have seen something from the OOM-killer in the syslog. I just double checked to make sure. On 23.03.20 20:58, Tormod Volden wrote: > 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. correct > Does the timestamp on your log indicate that xscreensaver died just > after killing molecule? yes > 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? Ah, that's not in the man page; I'll add it, but as currently the users aren't in the office, it'll take some time before we'll see results. Stay safe everyone, Jens Holzkämper Xorg.0.log.namor.gz Description: application/gzip
Bug#953098: xscreensaver: Crashes with XIO: fatal IO error
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 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.
Bug#953098: xscreensaver: Crashes with XIO: fatal IO error
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.
Bug#953098: xscreensaver: Crashes with XIO: fatal IO error
So, I tried another self compiled version, this time without any of the Debian patches to see if the crashes happen with a pure upstream version: They do (see attached log), so I'll inform upstream of the problem as well. > When using > xscreensaver -nosplash -log /tmp/x.log -verbose & > I did not see the XIO fatal IO error message.> > The crash was not accompanied by any useful information in the logfile. > If someone can advise how to get more information in the logfile, I'll > be happy to help investigate this bug. Adding the parameter -no-capture-stderr is needed to capture error messages during a xscreensaver-crash acording to the man-page. error 10 with 5.43-no-debian-patches.gz Description: application/gzip
Bug#953098: xscreensaver: Crashes with XIO: fatal IO error
xscreensaver crashes also in my system. Debian version: 10.3 (Buster) xscreensaver version: 5.42+dfsg1-1 My system (a laptop) has 3 screens: - the original one - connected via HDMI - connected via DisplayLink When using xscreensaver -nosplash -log /tmp/x.log -verbose & I did not see the XIO fatal IO error message. However, the message "xscreensaver-gl-helper did not report a GL visual!" repeated once in a while. Whatever it is, it did not cause xscreensaver to crash. The crash was not accompanied by any useful information in the logfile. If someone can advise how to get more information in the logfile, I'll be happy to help investigate this bug. On Wed, 04 Mar 2020 14:08:56 +0100 =?utf-8?q?Jens_Holzk=C3=A4mper?= < jens.holzkaem...@zbmath.org> wrote: > Package: xscreensaver > Version: 5.42+dfsg1-1 > Severity: grave > Tags: security > Justification: user security hole
