reopen 593303 thanks > xscreensaver-command sleeping three times for a second each. Here's a > patch to execute those sleeps in the background and half the time to > get the system suspended using the hot keys. It could be executed in > another half the time, but I haven't tracked that down.
Running these actions in parallel is probably fine, but what is not OK is to suspend the system before these actions have finished. I suggested a partly reverting patch in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700696#15 but maybe it is enough to add a "wait" command at the end of the script. FYI, I have fixed xscreensaver --lock to not wait an extra second when it is launched by a suspend action (well, anything not typed from a command line), see https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1229486/comments/9 http://anonscm.debian.org/gitweb/?p=collab-maint/xscreensaver.git;a=commitdiff;h=a48b6e029f6c2d93a0c88303b226efcff46bb23f > As a side note, throttling the screen saver and forcing dpms to off is > pointless when the cpu and graphics card are going to be powered off. Especially on older machines, it takes noticable time to launch some xscreensaver hacks. Throttling the screensaver before activating it avoids seeing the screensaver hack executing before the screen goes black. Best regards, Tormod -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
