On Wayland, if I lock my Plasma session and leave for several minutes, when I get back to the computer and type my password to unlock the session, in general some inputs are missed (my password is 6 characters long and only 5 "*" appear in the password field) ; I took the habit to type my password fast, without pressing any key before, since it works flawlessly on X11. But on Wayland, the first character I type is generally skipped. I think it also happen in SDDM. Plasma 5.13.4, Archlinux, KDE Frameworks 5.48.
I think that is intentional so the first key wakes up the screen first.
OK but on X11, it wakes the screen AND types my input. It's really convenient.
+1, need parity with the experience on X11.
Still valid in plasma 5.14.1, Arch Linux.
Still happening on Plasma 5.19.
Still happening in 5.20.
Hey, good news! Apparently there's now parity with the X11 experience - the X11 screen locker also eats the first character and doesn't pass it to the greeter. I'm not sure if its new as of 5.24, or appeared in one of the 5.25 pre-releases, but currently this behaves as follows, on X11: 1. Lock the screen using the screen locking shortcut (META+L). 2. Wait for the lock screen UI to show (on my system manual locking starts by blanking the screen, then the UI shows after a second or so). 3. Make sure the greeter is not showing and start typing "123". Expected Behavior: The greeter shows that 3 characters have been typed into the password entry field. Actual Behavior: The greeter shows that only 2 characters have been typed into the password entry field. More information: My password starts with a capital letter, so on my system the behavior is a bit sporadic because holding SHIFT also wakes up the greeter, so if I type the first capital letter slow enough, the greeter will be ready to receive the first character keydown correctly.
bizarre bug while trying to reproduce this bug on neon unstable: 1. open System Settings 2 wait for automatic screen locking 3. type your password Result: the screen is immediately unlocked when I start to type my password and sometimes my password appears in the search field of System Settings lol Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.25.80 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Graphics Platform: Wayland
There is a grace period with auto-lock where moving the mouse/typing disables the screenlock immediately. See the "allow unlocking without password for:" field
(In reply to David Edmundson from comment #9) > There is a grace period with auto-lock where moving the mouse/typing > disables the screenlock immediately. > > See the "allow unlocking without password for:" field You are right. Sorry for my laughable mistake. :( Regarding to the bug described in this report, I can also reproduce at least on Wayland. 1. set the time out to switch the screen off to 1 minute in power management settings 2. lock the screen 3. wait until the screen switches off 4. type your password and press enter Result: unlocking fails due to wrong password
On my use case - X11 - with the latest neon unstable kscreenlocker - 5.24.5+p22.04+tunstable+git20220603.0105-0 - the locker no longer eats the first char and all characters typed before the greeter shows the password entry field are entered correctly into the password entry field. The password entry field is also no longer masked by default, but this is another issue altogether...
As originally described the issue is now fixed in Plasma 5.25. I see unfortunately people have been reporting other issues in here too, so I'd like to request that folks able to reproduce them in Plasma 5.24 or 5.25 file new bug reports about them. Thanks everyone!