Bug 480449 - Pressing Enter after inserting the password on the login screen doesn't work
Summary: Pressing Enter after inserting the password on the login screen doesn't work
Status: RESOLVED DUPLICATE of bug 478875
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: 5.92.0
Platform: Neon Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: qt6
Depends on:
Blocks:
 
Reported: 2024-01-28 17:33 UTC by John
Modified: 2024-01-28 18:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description John 2024-01-28 17:33:43 UTC
SUMMARY
Pressing Enter after inserting the password on the login screen doesn't work, but on the lock screen it works


STEPS TO REPRODUCE
1. Start or restart until it reaches the login screen
2. Type your password
3. Press the Enter key on your keyboard


OBSERVED RESULT
Nothing happens
So you have to press with the mouse that arrow next to the password input field
If you lock the session from the start menu or pressing Supper + L, type password and press Enter, it works


EXPECTED RESULT
After pressing "Enter" the password is checked and if it's good it lets you login into the session, if not it tells you that the password is not good, so you can try again.
The login screen should work like the lock screen.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.92.90
KDE Frameworks Version: 5.249.0
Qt Version: 6.6.1

ADDITIONAL INFORMATION
KDE Neon fully updated, showing Plasma 6.0 RC1
Kernel Version: 6.5.0-15-generic (64-bit)
CPU: Intel® Core™ i5-8250U
GPU: Integrated UHD 620
-----------------------------------------------------------------
Sorry if this bug is not in the proper subsection, I could not find a login screen, isn't lock screen the same?
I also didn't find SDDM.

Thank you and please move it to the right section if you can or tell me how to do it or delete it / recreate in the proper place!
Comment 1 Doug 2024-01-28 17:52:11 UTC

*** This bug has been marked as a duplicate of bug 478875 ***