https://bugs.kde.org/show_bug.cgi?id=496061
--- Comment #2 from Richard Tippl <richard.ti...@gmail.com> --- 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 logging in leads to spamming of newlines. 2 - Holding space just for half a second before clicking "sleep" is also enough Following your reproduction attempt is also enough to trigger it. However I've come up with an idea while further testing it. The bug is commonly triggered in google chrome for me, and the editor i tested with is VS Code, both of these run through xwayland by default. I've tested it the following way: 1 - Run vscode and suspend system - key is spammed 2 - Run gedit and suspend system - key is NOT spammed 3 - Run vscode with --enable-features=UseOzonePlatform --ozone-platform=wayland - key is NOT spammed So the blame is probably not with chromium, but caused for me by chromium running through xwayland. However i don't have any xwayland text editor to test with. Can you try to reproduce it according to these instructions? However not sure anymore if this is caused by KDE, xwayland or somewhere in between... Side note, the window also doesn't have to immediately focus upon logging in. I usually test with yakuake, so once the terminal is closed, upon logging in the editor/browser is immediately focused. But i also tested it with Konsole and the spam is happening only after switching over to vscode, further confirming only a subset of windows is affected. -- You are receiving this mail because: You are watching all bug changes.
