On Wed, Nov 19, 2014 at 9:29 PM, Jamie Zawinski wrote: > On Nov 19, 2014, at 5:31 AM, John Goerzen wrote: > >> 3) When moving the mouse or pressing a key to wake up the screen and >> unlock it, frequently the previous content of the screen will show up >> for a few seconds before it is blanked and the logic box shown. > > That's because your machine was suspended -- CPU halted -- and what you are > seeing on the screen when it powers back on was put there by BIOS before the > CPU started running again. It halted the CPU with the screen not-yet-blanked, > from xscreensaver's perspective. Likewise, there is no way to fix this, > because Linux sucks. >
Where I have seen this, and bug reports thereof, the reason has been race conditions in the suspend scripts, that allow the hardware suspend to take place before xscreensaver has blanked the screen. Typically because someone had the idea of adding & to all commands to speed up the suspend sequence, and no "wait". I don't see why this cannot be fixed, Linux or not. Tormod -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
