GNOME Bugzilla – Bug 581016
pokes screensaver before computer suspends
Last modified: 2009-05-01 17:27:40 UTC
The way suspend is suppose to work is: - user selects suspend - screen locks - [machine stops] - [machine resumes] - g-p-m pokes screensaver to put up dialog or unblank Here's what seems to happen now: - user selects suspend - screen locks - g-p-m pokes screensaver to put up dialog or unblank - [machine stops] - [machine resumes] - screen lock has timed out
This is actually a devicekit-power bug. See https://bugzilla.redhat.com/show_bug.cgi?id=497563