[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-06 10:32:16
Message-ID: 4C330630.6000307 () invisiblethingslab ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On 07/06/10 11:39, Miha Čančula wrote:
> 2010/7/6 Joanna Rutkowska <joanna@invisiblethingslab.com>
> 
>> On 07/05/10 20:29, Stefan Majewsky wrote:
>>> 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.
>>>
>> Hmmm, but I sometimes see this problem even with composition disabled...
>>
>> joanna.
>>
> I've noticed it too on Arch, so it does happen, but I usually have
> composting enabled and I can't say if this is the cause. Either way, isn't
> bugs.kde.org the place for this?
> 
Before going to bugzilla, I was hoping to get either of the two:
1) Confirmation that screen is locked *before* suspend, and that this is
clearly a bug that I see the screen on resume,

2) Confirmation that the screen is locked *after* resume, and
explanation why this is done so this way.

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]