An XIO error means that the server dropped our connection, as opposed to the client making an invalid request, which is weird. Usually IO errors only happen when the X server crashes.
Maybe it's a driver bug? Maybe you're running out of memory? (Though typically the server sends a more sensible X error than this when out of memory.) However, the XScreenSaver daemon does not use XSHM, so that error message is probably coming from the display mode, not the daemon. A crash in the display mode won't cause the daemon to exit and the screen to unlock. As always, the only way to figure this out is if you include all of the output of -log. Also, you're running 5.45 instead of 6.00 and if you can't reproduce it in 6.00 there's no point in investigating any further. So try that. -- Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
