SUMMARY *** After a screen lock I press the enter key to wake up my monitors. I then type in my password and am rejected as invalid password. It looks like the enter key is being taken as part of the password input *** STEPS TO REPRODUCE 1. Start your desktop 2. Log into sddm 3. wait for screen saver to lock the computer 4. press enter to wake monitor 5. enter password to log in OBSERVED RESULT Your password is rejected as invalid EXPECTED RESULT The enter key should either "enter" the empty password or be disregarded as input on the first character input Your password should be accepted if it matches and you unlock the screensaver SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.2.15-300.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 20 × 12th Gen Intel® Core™ i7-1280P Memory: 62.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A8 ADDITIONAL INFORMATION
Are you saying that at step 4, when you wake up the monitor with the enter key, it inappropriately attempts to unlock the screen using an empty password?
(In reply to Nate Graham from comment #1) > Are you saying that at step 4, when you wake up the monitor with the enter > key, it inappropriately attempts to unlock the screen using an empty > password? It does not attempt to unlock the screen, but when I enter the password in correctly I get a password incorrect error back, as though the enter key was considered part of the password. On the second attempt i am allowed to enter the password and log in.
So the first time you try to enter your password, it's rejected, and the second time, it works? Can you elaborate on why you think the enter key is involved here, or is that a hypothesis at this point?
(In reply to Nate Graham from comment #3) > So the first time you try to enter your password, it's rejected, and the > second time, it works? Correct > > Can you elaborate on why you think the enter key is involved here, or is > that a hypothesis at this point? It is a hypothesis
Thanks. In step 4, if you wake the monitor by clicking the mouse or pressing a modifier key like Ctrl, does the problem still happen in step 5?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
UP