Bug 522842 - plasma-login-manager sometimes attempts login without any input from the user after waking from sleep
Summary: plasma-login-manager sometimes attempts login without any input from the user...
Status: RESOLVED DUPLICATE of bug 521900
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.7.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-07-09 08:09 UTC by kb.atlantic048
Modified: 2026-07-18 07:29 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kb.atlantic048 2026-07-09 08:09:36 UTC
DESCRIPTION
After waking from sleep, the plasma-login-manager will sometimes attempt to login without any input from the user, leading to unlock failure. This happens particularly when the login screen is shown instead of the time and date one.  
STEPS TO REPRODUCE
1. Make the computer sleep (suspend to ram)
2. Wake the up the computer
3. After the manager should attempt login without the user's decision

OBSERVED RESULT
the plasma-login-manager will sometimes attempt to login involuntarily after waking from sleep

EXPECTED RESULT
it should not attempt to login involuntarily

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44
KDE Plasma Version: 6.7.2
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1

ADDITIONAL INFORMATION
This is might be releated to 517874
Comment 1 Luca76 2026-07-14 11:25:24 UTC
Confirmed. On KDE Neon 6.7.2 updated. When I resume from sleep, and I write some keys (not enter), after one or two or three keystrokes (no ENTER key) the input box is disabled and it tries to login.
Comment 2 Nate Graham 2026-07-17 20:59:08 UTC
This is the screen locker, not the login manager. We have an existing bug report tracking the issue, too; marking this as a duplicate of it.

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