Created attachment 194110 [details] Output of journalctl -b | grep kscreenlocker DESCRIPTION If you press a key or use a mouse or laptop trackpad during the wake from sleep process, the lock screen will immediately submit the password as soon as you type a single character. STEPS TO REPRODUCE 1. Put the device into sleep (NOT screen turned off) 2. Wake the device up 3. While the device is waking up, press any key 4. Attempt to unlock device NOTE: Bug may be hardware specific, so hardware details have been included in the ADDITIONAL INFORMATION section. OBSERVED RESULT The single character in the password box is submitted as the password and used to attempt to unlock the device. EXPECTED RESULT The lock screen waits for you to hit the enter key or press the submit password button to submit the password and attempt to unlock the device. SOFTWARE/OS VERSIONS Operating System (available in the Info Center app, or by running `kinfo` in a terminal window): CachyOS Linux KDE Plasma Version: 6.7.2 KDE Frameworks Version: 6.27.0 Qt Version: 6.11.1 Kernel Version: 7.1.2-3-cachyos (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION ---Hardware--- Product Name: Alienware 16X Aurora AC16251 CPU: Intel Core Ultra 9 275HX GPU 1: Intel Graphics (integrated) GPU 2: NVIDIA GeForce RTX 5060 Laptop GPU (discrete)
> 4. Attempt to unlock device What does this mean, exactly? Does it mean "press the 'Enter' key or click the 'submit' button"? Or something else?
(In reply to Nate Graham from comment #1) > > 4. Attempt to unlock device > What does this mean, exactly? Does it mean "press the 'Enter' key or click > the 'submit' button"? Or something else? Attempt to enter your password. If the bug is present for you, you will probably notice the bug before having to press enter. Also, lately the bug has only sometimes been happening, so you may have to try a couple times in order to see it.
Aha! In that case this is the same issue as Bug 521900; you're encountering it in a slightly different way by to starting to type your password immediately. But it's the same issue. *** This bug has been marked as a duplicate of bug 521900 ***