Comment 8 for bug 1054299

This bug is younger than Bug #423930 and apparently this bug was also originally reported against xscreensaver. If this report is still handling a bug of xscreensaver, it should be marked as a duplicate of Bug #423930.

However, the end-user problem can be dealt by ensuring that "xscreensaver-command -lock" will be finished before suspending. That is done by running the xscreensaver-command and the possible script enclosing it on foreground and by letting them run succesfully before entering suspend mode. Thus the fix happens in the calling code, not necessarily in xscreensaver itself. For xfce4-session the calls of xflock4 script should be fixed, for lxsession, the calls of lxlock should be fixed, and xfce4-power-manager's call of xscreensaver-command might need fixing, too. As for xflock4 and lxlock, some alternative locking utilities, such as slock, should be run on background to let the script finish before user has unlocked the lock, so that e.g. suspend mode can be entered while session is locked.