[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Locking screen *before* suspend?
From:       Joanna Rutkowska <joanna () invisiblethingslab ! com>
Date:       2010-07-07 11:21:37
Message-ID: 4C346341.4050401 () invisiblethingslab ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On 07/06/10 11:55, Olivier Goffart wrote:
> Le Monday 05 July 2010, Stefan Majewsky a écrit :
>> On Monday 05 July 2010 12:12:05 Joanna Rutkowska wrote:
>>> It seems like KDE locks screen (via kscreenlocker) only after resume
>>> from suspend (e.g. S3 sleep), which results in the original content of
>>> the screen to be often visible for a second or more, and only afterwards
>>> the screen gets locked and the unlock password is expected.
>>
>> IMO, the screen *is* locked before suspending. That you get to see the
>> desktop for a short time is a compositing error.
> 
> The problem seems that starting the screen saver is sometimes too slow and we 
> do not wait the screen saver has finished loading before going to sleep.
> 
> Which mean that when the computer wakes up, the screen saver might still not 
> be running, and I can see the screen, and even interact with it for few 
> seconds. (Especially when the computer is on load) 
> 

This seems indeed the case. So, again, can we add a wait loop for the
screenlocker to fully engage and only afterwards proceed with the suspend?

joanna.


["signature.asc" (application/pgp-signature)]

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


[prev in list] [next in list] [prev in thread] [next in thread]