Bug 495396 - pressing enter or clicking the submit button won't unlock the screen, have to kill kscreenlocker_greet from virtual terminal
Summary: pressing enter or clicking the submit button won't unlock the screen, have to...
Status: RESOLVED DUPLICATE of bug 494927
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: 6.2.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-26 19:26 UTC by andy
Modified: 2024-10-28 16:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description andy 2024-10-26 19:26:32 UTC
SUMMARY
When I went to unlock my system today  it would not let me. I could type the password, but pressing enter did nothing, and clicking the submit button did nothing. I could from there still delete characters etc, the screen wasn't frozen, just not submitting. On other screens I could try entering the password there and same behaviour. I went to another virtual terminal and killed kscreenlocker_greet, and then went back and a new instance let me type the password and successfully unlocked the session.

STEPS TO REPRODUCE
1. Use computer for several days, at night turning off screen, in morning turning on screens and unlocking

OBSERVED RESULT
One day it will not unlock when you press Enter after typing the password on the unlock screen

EXPECTED RESULT
unlocks when you press Enter after typing the password on the unlock screen

SOFTWARE/OS VERSIONS
Operating System: Arch Linux vmlinuz-linux-lts.arch.20241021.1628.efi
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.6.57-1-lts (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Comment 1 andy 2024-10-26 19:27:57 UTC
also no relevant info seen in journalctl at the time
Comment 2 Nate Graham 2024-10-28 16:12:58 UTC

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