[Powerdevil] [Bug 457413] First character typed while the screen is in power saving mode is lost
https://bugs.kde.org/show_bug.cgi?id=457413 Natalie Clarius changed: What|Removed |Added CC||natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457413] First character typed while the screen is in power saving mode is lost
https://bugs.kde.org/show_bug.cgi?id=457413 Patrick Silva changed: What|Removed |Added Platform|Other |Archlinux Version|master |5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457413] First character typed while the screen is in power saving mode is lost
https://bugs.kde.org/show_bug.cgi?id=457413 --- Comment #8 from Nate Graham --- That makes sense when the screen's not locked, because otherwise by waking up your screen you'd have random characters typed somewhere on the screen. But when the screen is locked, I think it makes sense to allow input through so that you can wake up the screen and also unlock with the same thing. It would be the same principle by which we allow input through on the lock screen even when the interactive UI isn't visible yet. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457413] First character typed while the screen is in power saving mode is lost
https://bugs.kde.org/show_bug.cgi?id=457413 --- Comment #7 from Zamundaaa --- It was introduced with https://invent.kde.org/plasma/kwin/-/commit/57b11f84296b69944b907a89d403dc50d36a75dc, but the commit message doesn't really mention anything specific. I think it's to allow you to press any key without consequences in order to wake up the PC though, instead of having to care about what you press. It's also consistent with standby, where the input event for waking up is not passed on to the system either (which KWin has no control over, either the kernel or firmware does this) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457413] First character typed while the screen is in power saving mode is lost
https://bugs.kde.org/show_bug.cgi?id=457413 --- Comment #6 from Nate Graham --- Do you happen to know the reasoning behind it being an intentional behavior? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457413] First character typed while the screen is in power saving mode is lost
https://bugs.kde.org/show_bug.cgi?id=457413 --- Comment #5 from Patrick Silva --- (In reply to Zamundaaa from comment #4) > is this on Wayland, or on X? On Wayland, this is intentional and built into > KWin Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457413] First character typed while the screen is in power saving mode is lost
https://bugs.kde.org/show_bug.cgi?id=457413 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com --- Comment #4 from Zamundaaa --- is this on Wayland, or on X? On Wayland, this is intentional and built into KWin -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457413] First character typed while the screen is in power saving mode is lost
https://bugs.kde.org/show_bug.cgi?id=457413 Nate Graham changed: What|Removed |Added Component|greeter |general Status|REPORTED|CONFIRMED Severity|normal |minor Version|git-master |master Ever confirmed|0 |1 CC||m...@ratijas.tk Product|kscreenlocker |Powerdevil --- Comment #3 from Nate Graham --- Can reproduce. Seems like a powerdevil issue; it eats the keystroke, so it doesn't make it to the screen locker (or anything else; maybe the screen wasn't locked). -- You are receiving this mail because: You are watching all bug changes.
