https://bugs.kde.org/show_bug.cgi?id=496061
TraceyC changed:
What|Removed |Added
CC||kde...@tlcnet.info
--- Comment #6 from TraceyC ---
I
https://bugs.kde.org/show_bug.cgi?id=496061
David Edmundson changed:
What|Removed |Added
CC||elles.rob...@gmail.com
--- Comment #5 from Da
https://bugs.kde.org/show_bug.cgi?id=496061
Nate Graham changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=496061
--- Comment #4 from Richard Tippl ---
I've tried all 4 options and nothing has changed. (unless the options require a
reboot)
Also wanted to try with Discord, however after waking up it "spins" for a while
before network connection gets established, so
https://bugs.kde.org/show_bug.cgi?id=496061
--- Comment #3 from Nate Graham ---
Aha,so it's an issue that only affects either XWayland apps or XWayland-using
Chromium-based apps. That's an important clue indeed.
However I can't reproduce it when trying in Discord, which is both
Chromium-based a
https://bugs.kde.org/show_bug.cgi?id=496061
--- Comment #2 from Richard Tippl ---
That is very odd.
The exact cases for me are:
1 - I don't even need to hold the key, the instant the "enter" key is pressed
during confirmation of "systemctl suspend" is enough to trigger the bug, waking
up and logg
https://bugs.kde.org/show_bug.cgi?id=496061
Nate Graham changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Product|plasmashell
