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://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
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.
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.
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
https://bugs.kde.org/show_bug.cgi?id=316734
damian changed:
What|Removed |Added
CC||damik...@gmail.com
--
You are receiving this mail
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.
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
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
Priority|HI |VHI
Keywords|triaged
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
CC||korner...@protonmail.com
--- Comment #38 from
https://bugs.kde.org/show_bug.cgi?id=316734
Oliver Stoeneberg changed:
What|Removed |Added
CC||olive...@online.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
CC||damianator...@gmail.com
--- Comment #37 from
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
CC||christian.la...@gmx.net
--- Comment #36 from
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
CC||k...@web.de
--- Comment #35 from Nate Graham
https://bugs.kde.org/show_bug.cgi?id=316734
Tristan Miller changed:
What|Removed |Added
CC||psychon...@nothingisreal.co
https://bugs.kde.org/show_bug.cgi?id=316734
Patrick Silva changed:
What|Removed |Added
CC||bugsefor...@gmx.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
CC||goetzchr...@pm.me
--- Comment #34 from Nate
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
CC||dfloger...@gmail.com
--- Comment #33 from Nate
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
CC||kos...@koshka.ddns.net
--- Comment #32 from Nate
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
CC||kingspammernerd@protonmail.
|
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
CC||jgc.n...@gmail.com
--- Comment #30 from Nate
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
https://bugs.kde.org/show_bug.cgi?id=316734
Alois Wohlschlager changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
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
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
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
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
https://bugs.kde.org/show_bug.cgi?id=316734
Alois Wohlschlager changed:
What|Removed |Added
CC||alo...@gmx-topmail.de
--- Comment #24
https://bugs.kde.org/show_bug.cgi?id=316734
Alois Wohlschlager changed:
What|Removed |Added
CC||icohen2...@zoho.com
--- Comment #23 from
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.
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
https://bugs.kde.org/show_bug.cgi?id=316734
David Edmundson changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=316734
Apoorv Potnis changed:
What|Removed |Added
Ever confirmed|1 |0
Resolution|WAITINGFORINFO
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
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
https://bugs.kde.org/show_bug.cgi?id=316734
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
https://bugs.kde.org/show_bug.cgi?id=316734
Andrey Melentyev changed:
What|Removed |Added
CC||and...@psyduck.se
--- Comment #16 from
https://bugs.kde.org/show_bug.cgi?id=316734
David Edmundson changed:
What|Removed |Added
CC||apoorvpot...@gmail.com
--- Comment #15 from
https://bugs.kde.org/show_bug.cgi?id=316734
soredake changed:
What|Removed |Added
CC||ndrzj1...@relay.firefox.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=316734
OlafLostViking changed:
What|Removed |Added
CC||olaf.the.lost.viking@gmail.
https://bugs.kde.org/show_bug.cgi?id=316734
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REOPENED
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.
https://bugs.kde.org/show_bug.cgi?id=316734
firewalker changed:
What|Removed |Added
Resolution|WORKSFORME |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=316734
Andrew Crouthamel changed:
What|Removed |Added
Resolution|WAITINGFORINFO |WORKSFORME
Status|NEEDSINFO
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.
https://bugs.kde.org/show_bug.cgi?id=316734
Andrew Crouthamel changed:
What|Removed |Added
Keywords||triaged
--- Comment #9 from Andrew
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
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
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
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
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
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
https://bugs.kde.org/show_bug.cgi?id=316734
Kai Uwe Broulik changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
54 matches
Mail list logo