Re: [trinity-devel] Fixed reaching fully activated state in screen saver - tde-devels

28 Oct 2013

...
 To test the problem, which was fixed, it is simple:
1) Make sure that you have enabled lock screen before suspend or 
standby.
2) Set the screen saver run after a short time.
3) Once the screensaver is activated, press button to go into 
suspend mode. Or 
set in tdepowersave autosuspend for a short time => a little 
longer than time 
to activate screen saver.
4) Look, that nothing happens (for any length of time), until you 
cause an 
activity that will lead to stop screen saver.
5) Only after stopping screen saver follows immediately switch 
into desired 
suspend mode. 
I tested tdepowersave before applying the patch. In tdepowersave I 
set the screensaver to 1 minute and autosuspend to 2 minutes. 
Without the patch the following happens:

* After 1 minute the screensaver starts.
* After 2 minutes the suspend-to-ram 30 second timeout dialog does 
not appear.
* Thereafter the laptop never automatically goes into suspend-to-
ram mode by itself.
* Any user action interrupts the screensaver.
* The laptop then goes into suspend-to-ram mode and the suspend-to-
ram 30 second timeout dialog never appears.

With the patch:

* After 1 minute the screensaver starts.
* After 2 minutes the suspend-to-ram 30 second timeout dialog 
appears.
* After 30 seconds the laptop automatically goes into suspend-to-
ram mode by itself.
* Upon restoring from suspend-to-ram, the screensaver lock dialog 
appears.

Well done!

Darrell