[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #46 from Martin Flöser  ---
Based on comment #43 I read through the relevant code pieces for Wayland. On
Wayland we ensure that when the screen is locked only the lock screen window or
input method window should be visible (see
https://invent.kde.org/plasma/kwin/-/blob/v5.22.4/src/composite.cpp#L608 ). As
stated in comment #43 this seems to not work correctly.

By investigating I found two smallish issues which might cause it:
1. There seems to be no full repaint triggered when the screenlocker reports to
get locked. In the handler for the aboutToLock signal (see
https://invent.kde.org/plasma/kwin/-/blob/v5.22.4/src/wayland_server.cpp#L604 )
a full repaint needs to be triggered. This would ensure that KWin stops
rendering all windows before the lock screen gets shown. Thus the screen should
turn black. (Please note that the code in Kscreenlocker needs to be adjusted as
the emit happens before the lock state is changed to AcquiringLock. Maybe a
dedicated signal is needed, see
https://invent.kde.org/plasma/kscreenlocker/-/blob/v5.22.4/ksldapp.cpp#L380).

2. KWin reports the screen as fully locked once the window for the lock screen
is registered (see
https://invent.kde.org/plasma/kwin/-/blob/v5.22.4/src/wayland_server.cpp#L245
). At that time it is not yet rendered, not yet even damaged. It is only
created. The screenlocker immediately removes the inhibition and the system
suspends (see
https://invent.kde.org/plasma/kscreenlocker/-/blob/v5.22.4/ksldapp.cpp#L720 and
https://invent.kde.org/plasma/kscreenlocker/-/blob/v5.22.4/ksldapp.cpp#L301 ).
This needs to be changed to wait for
a) surface fully damaged
b) composition pass finished
c) screen presented (e.g. drm frame callback)

In combination these two issues can create a race condition where the screen
stays in the content of the unlocked state. Still it is likely for many systems
to not hit the issue. E.g. anything triggering a repaint between aboutToLock
and Wayland window created will ensure the screen to go black. This can e.g.
happen when clicking a button to suspend (the button release of the mouse will
do) or when closing a notebook lid by triggering the common fake touchpad moves
in these cases. This especially explains the pinephone case where the system is
probably not put to lock through a pointer/touch event.

The second issue explains why the problem came back. The code was written
against the wl_shell interface and got migrated over the years to xdg_shell
which is a more complex interface and needs more time to setup thus the too
early removed inhibition is more likely to cause issues.

Of course this is only for Wayland. For X11 we need other solutions which might
be possible to reuse ideas from Wayland.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[damian]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #45 from damian  ---
(In reply to Martin Flöser from comment #42)
> Can those affected by the problem please check dmesg after a suspend cycle
> for messages related to drm?

I checked the dmesg output, I could not find anything related to drm but maybe
I am doing something wrong:

https://pastebin.com/akidDFGn


> 
> Personally I haven't experienced this problem for years (!) any more and
> given the past I fear that this is a driver issue. Which can make it
> difficult to investigate. We might need much more information from everyone
> experiencing this issue. It is possible that this is a driver/distro
> specific problem.
> 
> Thus I would like anybody experiencing the problem as first step try whether
> the issue also persist on a Wayland session. This is extremely important to
> know whether the problem is only X11 specific or also on Wayland and thus in
> general.

I could not reproduce on Wayland, X11 I can reproduce consistently.

> 
> Then further I would like every affected user to report:
>  * Distribution and version
>  * Mesa version
>  * Hardware (which CPU and GPU)

Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-63-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-2520M CPU @ 2.50GHz
Graphics Processor: Mesa DRI Intel® HD Graphics 3000
Mesa version: 20.2.6

> 
> This should hopefully give us some more information to understand who is
> affected and why.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[firewalker]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #44 from firewalker  ---
Over the years I have seen it happening with nvidia open/closed drivers, ATI
open/closed drivers, intel gpus and now amdgpu.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Oliver Stoeneberg]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #43 from Oliver Stoeneberg  ---
It happens on the PinePhone running Manjaro Plasma Mobile with all the latest
updates installed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Martin Flöser]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #42 from Martin Flöser  ---
Can those affected by the problem please check dmesg after a suspend cycle for
messages related to drm?

Personally I haven't experienced this problem for years (!) any more and given
the past I fear that this is a driver issue. Which can make it difficult to
investigate. We might need much more information from everyone experiencing
this issue. It is possible that this is a driver/distro specific problem.

Thus I would like anybody experiencing the problem as first step try whether
the issue also persist on a Wayland session. This is extremely important to
know whether the problem is only X11 specific or also on Wayland and thus in
general.

Then further I would like every affected user to report:
 * Distribution and version
 * Mesa version
 * Hardware (which CPU and GPU)

This should hopefully give us some more information to understand who is
affected and why.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[damian]

https://bugs.kde.org/show_bug.cgi?id=316734

damian  changed:

   What|Removed |Added

 CC||damik...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[firewalker]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #41 from firewalker  ---
Even if you minimize everything, some times after waking the system, if the
mouse is moved, the screen locker will not show up at all.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #40 from christian.la...@gmx.net ---
I can not believe that this security issue is still not fixed after so many
years. The only workaround is to minimize all windows before you suspend your
workstation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

   Priority|HI  |VHI
   Keywords|triaged |

--- Comment #39 from Nate Graham  ---
Bumping up to VHI due to number of duplicates.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 CC||korner...@protonmail.com

--- Comment #38 from Nate Graham  ---
*** Bug 439814 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Oliver Stoeneberg]

https://bugs.kde.org/show_bug.cgi?id=316734

Oliver Stoeneberg  changed:

   What|Removed |Added

 CC||olive...@online.de

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 CC||damianator...@gmail.com

--- Comment #37 from Nate Graham  ---
*** Bug 405993 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 CC||christian.la...@gmx.net

--- Comment #36 from Nate Graham  ---
*** Bug 421320 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 CC||k...@web.de

--- Comment #35 from Nate Graham  ---
*** Bug 392303 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Tristan Miller]

https://bugs.kde.org/show_bug.cgi?id=316734

Tristan Miller  changed:

   What|Removed |Added

 CC||psychon...@nothingisreal.co
   ||m

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Patrick Silva]

https://bugs.kde.org/show_bug.cgi?id=316734

Patrick Silva  changed:

   What|Removed |Added

 CC||bugsefor...@gmx.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 CC||goetzchr...@pm.me

--- Comment #34 from Nate Graham  ---
*** Bug 366317 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 CC||dfloger...@gmail.com

--- Comment #33 from Nate Graham  ---
*** Bug 364915 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|CONFIRMED
   Priority|NOR |HI

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 CC||kos...@koshka.ddns.net

--- Comment #32 from Nate Graham  ---
*** Bug 415362 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 CC||kingspammernerd@protonmail.
   ||com

--- Comment #31 from Nate Graham  ---
*** Bug 414414 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 CC||jgc.n...@gmail.com

--- Comment #30 from Nate Graham  ---
*** Bug 408493 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #29 from David Edmundson  ---
>Could the issue described in comment 6 be worked around by blocking the 
>suspend util two (or maybe even three) frames of the lockscreen have been 
>rendered?

That's exactly what it does.

Based on the new software rendering test, what I suspect happens is
kscreenlocker is fullscreen and kwin is showing the kscreenlocker window.


We have seen in the past OpenGL clients when creating a new buffer have leaked
contents representing an old backbuffer. We could be in that situation if we're
processing screen removal and additons which kscreenlocker will treat as a new
window.

We typically guard that with sync requests, but because the screenlocker is an
override-redirect, that could potentially skipped.

We would need some way to prove that - and if so the fix, somewhat counter
intuitively, would be to slow down the screenlocker_greet mapping after
creation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Alois Wohlschlager]

https://bugs.kde.org/show_bug.cgi?id=316734

Alois Wohlschlager  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #28 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Alois Wohlschlager]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #27 from Alois Wohlschlager  ---
For me it is the opposite behavior. With GPU rendering, I cannot reproduce the
bug reliably. Sometimes I see the session content before the lockscreen
appears, sometimes I see a black screen with mouse cursor. In software
rendering mode, the session is always visible briefly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Isaac Cohen]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #26 from Isaac Cohen  ---
Also, I should point out that for me this issue only began when I upgraded to
Plasma 5.21. When I used 5.19 it never happened and after I upgraded it
happened every time. When filing my big report I actually saw this one but
noticed it was from several years ago and so figured it must be a different
issue (since mine just started with 5.21). So I filed a separate bug report but
it was marked a duplicate of this one. I guess it is the same issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Isaac Cohen]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #25 from Isaac Cohen  ---
(In reply to David Edmundson from comment #20)
> I have a theory to rule out:
> 
> If someone can reproduce this reliably, could they run "kcmshell5
> qtquicksettings" and set their backend to software and see if the screen
> locker issue perists or goes away

I could reproduce reliably. I tried what you said and now it works every time.
Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Alois Wohlschlager]

https://bugs.kde.org/show_bug.cgi?id=316734

Alois Wohlschlager  changed:

   What|Removed |Added

 CC||alo...@gmx-topmail.de

--- Comment #24 from Alois Wohlschlager  ---
Could the issue described in comment 6 be worked around by blocking the suspend
util two (or maybe even three) frames of the lockscreen have been rendered?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Alois Wohlschlager]

https://bugs.kde.org/show_bug.cgi?id=316734

Alois Wohlschlager  changed:

   What|Removed |Added

 CC||icohen2...@zoho.com

--- Comment #23 from Alois Wohlschlager  ---
*** Bug 436751 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Andrey]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #22 from Andrey  ---
Doesn't reproduce reliable over here unfortunately, only happens every once in
a while.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #21 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=316734

David Edmundson  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 Resolution|--- |WAITINGFORINFO

--- Comment #20 from David Edmundson  ---
I have a theory to rule out:

If someone can reproduce this reliably, could they run "kcmshell5
qtquicksettings" and set their backend to software and see if the screen locker
issue perists or goes away

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Apoorv Potnis]

https://bugs.kde.org/show_bug.cgi?id=316734

Apoorv Potnis  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Bug Janitor Service]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #19 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Andrey]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #18 from Andrey  ---
(In reply to David Edmundson from comment #17)
> >What kind of information do you need?
> 
> Anything that disproves the comment in #6

Not the person you were asking, but I also experience the issue. 

I'm not sure which statement from the comment #6 you want disproved, but my
system has Coffee Lake or Cannon Lake architecture. I have another laptop with
some Intel Gen 8 platform that is also affected.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=316734

David Edmundson  changed:

   What|Removed |Added

 CC||k...@davidedmundson.co.uk
 Resolution|--- |WAITINGFORINFO
 Status|CONFIRMED   |NEEDSINFO

--- Comment #17 from David Edmundson  ---
>What kind of information do you need?

Anything that disproves the comment in #6

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Andrey Melentyev]

https://bugs.kde.org/show_bug.cgi?id=316734

Andrey Melentyev  changed:

   What|Removed |Added

 CC||and...@psyduck.se

--- Comment #16 from Andrey Melentyev  ---
I see this quite regularly on the latest Plasma on Arch Linux and it looks like
quite a serious security / privacy issue. Happy to help debugging if anyone
offers a direction.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[David Edmundson]

https://bugs.kde.org/show_bug.cgi?id=316734

David Edmundson  changed:

   What|Removed |Added

 CC||apoorvpot...@gmail.com

--- Comment #15 from David Edmundson  ---
*** Bug 433893 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[soredake]

https://bugs.kde.org/show_bug.cgi?id=316734

soredake  changed:

   What|Removed |Added

 CC||ndrzj1...@relay.firefox.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[OlafLostViking]

https://bugs.kde.org/show_bug.cgi?id=316734

OlafLostViking  changed:

   What|Removed |Added

 CC||olaf.the.lost.viking@gmail.
   ||com

--- Comment #14 from OlafLostViking  ---
Still valid.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=316734

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Status|REOPENED|CONFIRMED

--- Comment #13 from Nate Graham  ---
I still see this occasionally.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[firewalker]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #12 from firewalker  ---
What kind of information do you need?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[firewalker]

https://bugs.kde.org/show_bug.cgi?id=316734

firewalker  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Andrew Crouthamel]

https://bugs.kde.org/show_bug.cgi?id=316734

Andrew Crouthamel  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #11 from Andrew Crouthamel  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The
bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki
located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[firewalker]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #10 from firewalker  ---
What kind of info do you need?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Andrew Crouthamel]

https://bugs.kde.org/show_bug.cgi?id=316734

Andrew Crouthamel  changed:

   What|Removed |Added

   Keywords||triaged

--- Comment #9 from Andrew Crouthamel  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information as soon as possible and set the bug
status as REPORTED. Due to regular bug tracker maintenance, if the bug is still
in NEEDSINFO status with no change in 30 days, the bug will be closed as
RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki
located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug
status as REPORTED so that the KDE team knows that the bug is ready to be
confirmed.

Thank you for helping us make KDE software even better for everyone!

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #8 from Martin Gräßlin  ---
So I just tried again on my Wayland system:
* screen goes black
* system suspends
* press power
* system wakes up
* shows old content
* shows lock screen

If it would use the last buffer before suspend, it were black and not old
screen content.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Josef Kufner via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #7 from Josef Kufner  ---
Can't it be because of double/tripple buffering? If only the first frame is
really rendered, the other half of the buffer will still contain previous
screen and after resume the buffers may not be swapped correctly, and if it
takes a while to redraw... What if the screen is cleared twice with a sync both
in between and after? (Just a wild guess.)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #6 from Martin Gräßlin  ---
(In reply to Josef Kufner from comment #5)
> The buffer must be cleared before suspend. Accordin to what I met in systemd
> configuration, It should be possible to "inhibit" suspend proces until the
> buffer is cleared.

well that's what we do from kscreenlocker. We adjusted the code to keep the
inhibition around till the first frame is definitely rendered. Nevertheless we
get an old buffer shown on resume. It works fine on my IvyBridge based system,
it doesn't on my SandyBridge based system.

Sorry, but as far as I investigated on my system our code does the right thing.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Josef Kufner via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #5 from Josef Kufner  ---
The buffer must be cleared before suspend. Accordin to what I met in systemd
configuration, It should be possible to "inhibit" suspend proces until the
buffer is cleared.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Martin Gräßlin via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #4 from Martin Gräßlin  ---
As far as I experience the problem, it's unfortunately not in our scope to fix
it. I even see the problem on my Wayland system which actually ensures that no
windows are rendered when the screen is locked. The DRM subsystem seems to
present an old buffer on resume.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Josef Kufner via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=316734

--- Comment #3 from Josef Kufner  ---
Since this is matter of security/privacy, the answer should be in form of
commit id ;)

I tested it right now and screen went black instead of showing the desktop, but
I'm not sure whether it is really fixed because my laptop is not in heavy load.
(I have something between 5.5 and 5.6)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 316734] The desktop gets displayed for couple seconds after waking the system.

[Kai Uwe Broulik via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=316734

Kai Uwe Broulik  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
Version|4.10.1  |unspecified
Product|ksmserver   |kscreenlocker
   Assignee|l.lu...@kde.org |plasma-b...@kde.org
 CC||bhus...@gmail.com,
   ||k...@privat.broulik.de,
   ||mgraess...@kde.org
 Resolution|--- |WAITINGFORINFO
  Component|general |greeter

--- Comment #2 from Kai Uwe Broulik  ---
Is that still an issue in Plasma 5.6?

-- 
You are receiving this mail because:
You are watching all bug changes.