'Re: Locking screen *before* suspend?'

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

List:       kde-devel
Subject:    Re: Locking screen *before* suspend?
From:       Dario Freddi <drf54321 () gmail ! com>
Date:       2010-07-07 9:36:37
Message-ID: 4C344AA5.7020206 () gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/signed)]

[Attachment #4 (multipart/alternative)]

 On 06/07/2010 12:32, Joanna Rutkowska wrote:
> 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,

The screen is always locked before suspending, also because there's no
way to lock the screen afterwards, as we don't get any signaling upon
resuming.

This is a known problem with the screen locker which is also
reproducible with the screensaver, IIRC.

> 2) Confirmation that the screen is locked *after* resume, and
> explanation why this is done so this way.
>
> joanna.
>
>
>
>  
>>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[Attachment #7 (text/html)]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    On 06/07/2010 12:32, Joanna Rutkowska wrote:
    <blockquote cite="mid:4C330630.6000307@invisiblethingslab.com"
      type="cite">
      <pre wrap="">On 07/06/10 11:39, Miha Čančula wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">2010/7/6 Joanna Rutkowska <a class="moz-txt-link-rfc2396E" \
href="mailto:joanna@invisiblethingslab.com">&lt;joanna@invisiblethingslab.com&gt;</a>

</pre>
        <blockquote type="cite">
          <pre wrap="">On 07/05/10 20:29, Stefan Majewsky wrote:
</pre>
          <blockquote type="cite">
            <pre wrap="">On Monday 05 July 2010 12:12:05 Joanna Rutkowska wrote:
</pre>
            <blockquote type="cite">
              <pre wrap="">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.
</pre>
            </blockquote>
            <pre wrap="">
IMO, the screen *is* locked before suspending. That you get to see the
</pre>
          </blockquote>
          <pre wrap="">desktop
</pre>
          <blockquote type="cite">
            <pre wrap="">for a short time is a compositing error.

</pre>
          </blockquote>
          <pre wrap="">Hmmm, but I sometimes see this problem even with composition \
disabled...

joanna.

</pre>
        </blockquote>
        <pre wrap="">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?

</pre>
      </blockquote>
      <pre wrap="">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,
</pre>
    </blockquote>
    <br>
    The screen is always locked before suspending, also because there's
    no way to lock the screen afterwards, as we don't get any signaling
    upon resuming.<br>
    <br>
    This is a known problem with the screen locker which is also
    reproducible with the screensaver, IIRC.<br>
    <br>
    <blockquote cite="mid:4C330630.6000307@invisiblethingslab.com"
      type="cite">
      <pre wrap="">
2) Confirmation that the screen is locked *after* resume, and
explanation why this is done so this way.

joanna.

</pre>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">Visit <a class="moz-txt-link-freetext" \
href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> \
to unsubscribe &lt;&lt; </pre>
        </blockquote>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>

["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] 