| Summary: | graceLockTimer value is too high | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | grayich <greyich> |
| Component: | Screen locking | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED LATER | ||
| Severity: | normal | CC: | bizyaev, kde, olib141 |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
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 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. |
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