Bug 488991 - Wrong password delay should respect PAM nodelay setting
Summary: Wrong password delay should respect PAM nodelay setting
Status: RESOLVED DUPLICATE of bug 407473
Alias: None
Product: plasmashell
Classification: Plasma
Component: Theme - Breeze (show other bugs)
Version: 6.1.0
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-22 17:31 UTC by liusen
Modified: 2024-06-22 17:36 UTC (History)
2 users (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 liusen 2024-06-22 17:31:14 UTC
SUMMARY
When I type in a wrong password on the KDE lock screen, the input field is grayed out for three seconds and I must wait to try again. This behavior should be optional.

STEPS TO REPRODUCE
1. Log in
2. Lock screen
3. Type in wrong password

OBSERVED RESULT
The password field is grayed out for three seconds.

EXPECTED RESULT
I wish for there to be no delay, or equally as good -- a delay of around 100ms.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.9.5-200.fc40.x86_64 
(available in About System)
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1

ADDITIONAL INFORMATION

A similar bug is here: https://bugs.kde.org/show_bug.cgi?id=415443

The difference is that I have to patch LockScreenUi.qml(https://invent.kde.org/plasma/plasma-desktop/-/blob/master/desktoppackage/contents/lockscreen/LockScreenUi.qml?ref_type=heads#L175)

--- LockScreenUi.qml.bak        2024-06-23 01:09:06.086202679 +0800
+++ LockScreenUi.qml    2024-06-23 01:10:00.025159058 +0800
@@ -172,7 +172,7 @@
         }
         Timer {
             id: graceLockTimer
-            interval: 3000
+            interval: 100
             onTriggered: {
                 root.clearPassword();
                 authenticator.startAuthenticating();
Comment 1 Nate Graham 2024-06-22 17:36:59 UTC

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