So what's happening is this: 1: screen is not locked. 2: you close the lid. 3: CPU halts. 4: hours pass. 5: you open the lid. 6: CPU starts up. 7: X server redraws the previous screen contents. 8: oh hey, the screen is still not locked, because the machine is just like it was before, except now the disk is thrashing. 9: eventually xscreensaver gets scheduled again, and notices that the clock has jumped. 10: xscreensaver says "oh shit!" and locks the screen.
What you are experiencing is the gap between steps 7 and 10. I gather that some Linux systems have a way for a script to run between steps 2 and 3, to run "xscreensaver-command -lock" and wait for it to complete before halting the CPU, which would solve this problem. I also gather that there is little agreement between the various Linux distros as to what that script is called or how you install it. So -- beats me! Another workaround, of course, is to lock your screen before closing the lid. -- Jamie Zawinski http://www.jwz.org/ http://www.dnalounge.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
