Bug 513491 - graceLockTimer value is too high
Summary: graceLockTimer value is too high
Status: RESOLVED LATER
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.5.4
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-17 16:48 UTC by grayich
Modified: 2025-12-17 21:04 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description grayich 2025-12-17 16:48:15 UTC 
in the /usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml file :
        Timer {
            id: graceLockTimer
            interval: 3000
            onTriggered: {
                root.clearPassword();
                authenticator.startAuthenticating();
            }
interval 3000 is very much, because this value is added to the system one (usually 3000), in total it turns out 6000++

IMHO, it's worth changing the value to 0 or 1
Comment 1 grayich 2025-12-17 16:55:05 UTC 
At the same time, in the /usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/logout/Logout.qml file, you can reduce the "property real timeout: 30" to 5, IMHO - 30 is too much

thanks
Comment 2 David Edmundson 2025-12-17 21:04:52 UTC 
We need to sync it up to the system value rather than selecting which random hardcoded value to choose as that will still be equally wrong.