*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY Two possible ways to reproduce: 1. In Settings/Power Management, configure "Turn off screen" after some amount of minutes. I also have "When locked: 1 minute" 2. Wait for screens to lock and turn off 3. Start typing your password. Other way: 1. lock screen 2. press escape to blank screen 3. start typing password OBSERVED RESULT The first letter/key press which "woke" the screens is lost and will not be part of the password. This means I have started to move the mouse, press some random key and then type the password after the screen locker UI has started showing. I also observe the enter key not always registering when typing my password quickly, but maybe that's another bug/unrelated... EXPECTED RESULT I expect to be able to start typing my password while the screens are off, including pressing enter. I'm quite sure that's how it used to work and according to https://bugs.kde.org/show_bug.cgi?id=472319 it's supposed to be the intended behavior. Maybe it was somehow introduced by the escape -> blank feature? SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20260209 KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.2 Kernel Version: 6.18.4-1-default (64-bit) Graphics Platform: Wayland I have two screens, but afaik this is an issue with single-screen setups as well. Someone on the kde help channel on matrix reproduced the escape-reproduction at least.
I can reproduce this on Plasma built from git-master. When the screen is off, the first character I type brings up the SDDM background, but not the password input. The second character typed is entered into the password input.
I am not entirely sure that this is unexpected. If, for instance, you were logged in and had a text editor open, and the screen turned off, you would expect to press a key to wake the screen without having it entered into the application. The same blocking (or, event consumption) is applied to mouse click, but not mouse movement (or perhaps, only the first tiny mouse movement which is effectively unnoticeable).
Pursuant to my rationale above, I'm marking this as RESOLVED INTENTIONAL. We won't change this exclusively for kscreenlocker (or PLM which now has the same behaviour). It may be the case that some people expect the first input to not be consumed for waking the screen and to go to applications anyway, so I think a feature request bug could be opened for the behaviour in general. I believe KWin is responsible for this.
(In reply to Oliver Beard from comment #2) > I am not entirely sure that this is unexpected. This directly contradicts what Nate had said in the other report as well as in a feature request to reject the first character entered https://bugs.kde.org/show_bug.cgi?id=514945 > This is a feature request to add a configuration option to reject keypresses on screen locker if the password entry is not visible. That was rejected, therefore this is a bug. Respectfully, I'm reopening this.
.
After re-reading the two reports, and some discussion with maintainers, the main difference between this and 514945 is 514945 - The screen is already awake, key presses go directly to the password input. This is expected This report - The screen is asleep, the first key press wakes the screen, the rest of the key presses are sent to the password input. This is also expected. My apologies for the confusion, I'll close this back out.
I'm not sure I understand, apologies if I'm being dense. According to https://bugs.kde.org/show_bug.cgi?id=472319 this behavior is not intentional, right? It seems to involve waking the screen, not just the input field being invisible/inactive. Also, when switching from wayland to X11 the behavior is different. In other words, using X11, when I lock the screen, press escape to blank it the first character I press both wakes/unblanks the screens *and* is used as the first character to the password input field. Is this behavior (which is new from my POV coming for X11) expected due to technical limitations around wayland, or is it expected because the UX is as expected? I'm just one user, but this change means that I need to wait 5-10 seconds before I can log in whereas before I could simply start typing my password and be logged in when the screens finished waking up. At least one of my screens is quite slow to wake.