Bug 481808

Confirming as I can reproduce (also git master). 
I wonder if this is an issue with the source build or if this is reproducible on regular installs.

I am able to reproduce this bug on an install of Plasma6 on Solus, installed through a private repo where we're testing it

Confirmed on neon unstable.

Interesting, I cannot reproduce the issue. I do have fingerprint auth enabled, so maybe that changes the behavior somehow.

Confirmed, also seeing this with 6.0.1.

I can confirm that with 6.0.0 on Gentoo, but it happens only happens start from the 3rd sleep cycle. Logging in reset the failure count.

I also have this problem. The sleep also takes a while to do but that may just be a me problem. Also having memory problems with high usage that seem to build up over time, with all apps closed I'm idle on 3GB but have no idea if it's related. Spamming sleep also gets you locked out, had to wait 10 minutes for it to let me enter my password.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.6.30-2-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7730U with Radeon Graphics
Memory: 7.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: Micro-Star International Co., Ltd.
Product Name: Modern 15 B7M
System Version: REV:1.0

*** Bug 488484 has been marked as a duplicate of this bug. ***

Never mind, I can reproduce it. The key for me is to go to sleep twice. Steps to reproduce for me:

1. Meta+L to lock
2. Click sleep button
3. Wake up machine (in my case, by briefly pressing the power button)
4. Click sleep again

It will now shake and then sleep, and then when waking up from sleep, shake again — in both cases displaying the failed login attempt text.

Confirming this issue with my setup. Has existed since Plasma 6 rolled out.

Operating System: EndeavourOS 
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.3
Kernel Version: 6.11.3-nitrous (64-bit)
Graphics Platform: Wayland

*** Bug 496152 has been marked as a duplicate of this bug. ***

Adding the phrase "Unlocking failed" for better search results.

Does it every time for me.

Comment 7's report that "Spamming sleep also gets you locked out" confirms what I suspected, but I can't confirm personally because I don't know how to configure that (something to do with PAM's faillock?).  So this is not merely cosmetic but fairly important.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro, linux 6.11.10-2-MANJARO x86_64
KDE Plasma Version: 6.2.4
KDE Frameworks Version: 6.8.0 
Qt Version: 6.8.1

*** Bug 499118 has been marked as a duplicate of this bug. ***

*** Bug 500451 has been marked as a duplicate of this bug. ***

Clicking on sleep in lockscreen also turns on fingerprint reader (500451), and in my case, turns on facial recognition (howdy)

It happens to me on ArchLinux with Wayland. I did it twice and journalctl showed:

Feb 16 23:13:42 kscreenlocker_greet[88142]: pam_unix(kde:auth): unexpected response from failed conversation function
Feb 16 23:13:42 kscreenlocker_greet[88142]: pam_unix(kde:auth): conversation failed
Feb 16 23:13:42 kscreenlocker_greet[88142]: pam_unix(kde:auth): auth could not identify password for []
Feb 16 23:13:51 kscreenlocker_greet[88142]: pam_unix(kde:auth): unexpected response from failed conversation function
Feb 16 23:13:51 kscreenlocker_greet[88142]: pam_unix(kde:auth): conversation failed
Feb 16 23:13:51 kscreenlocker_greet[88142]: pam_unix(kde:auth): auth could not identify password for []
Feb 16 23:13:58 kscreenlocker_greet[88142]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000)
Feb 16 23:13:58 kscreenlocker_greet[88142]: Failed to write to the pipe: Bad file descriptor.

Recently stumbled upon this issue too. 

OS: Arch Linux 
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.12.13-1-lts (64-bit)
Graphics Platform: Wayland

I also experienced this today by accident.
I tried a bit too often to get my PC to sleep, and was then locked out like when I really enter my password multiple times (I think the limit was 3?) incorrectly.

FYI, you don't have to wait 10 minutes:
At least, if you don't have any open files or something else that could get corrupted with a hard reset, you can just power off the PC and the timeout is gone.

*** Bug 504961 has been marked as a duplicate of this bug. ***

>At least, if you don't have any open files or something else that could get corrupted with a hard reset, you can just power off the PC and the timeout is gone.

You can also run 

`sudo faillock --user david --reset` from a TTY.

If anyone can reliably reproduce, I need some more output. 

Please can you run the following:

❯ QT_LOGGING_RULES=kscreenlocker_greet.debug=true /opt/kde6/lib/libexec/kscreenlocker_greet --testing
and  reproduce the issue.

Also can you share /etc/pam.d/kde  (they differ per distro)

and output of `faillock --user $USER`

I can reproduce it. Here's the requested information:



$ QT_LOGGING_RULES='kscreenlocker_greet.debug=true' ~/kde/usr/lib64/libexec/kscreenlocker_greet --testing
kscreenlocker_greet: Greeter is starting up.
kscreenlocker_greet: [PAM worker kde-smartcard] start: successfully started
kscreenlocker_greet: [PAM worker kde-fingerprint] start: successfully started
kscreenlocker_greet: [PAM worker kde] start: successfully started
kscreenlocker_greet: Greeter is running in testing mode
kscreenlocker_greet: Testing mode enabled: true
Locked at 1749055944
qml: The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration!
kscreenlocker_greet: PamAuthenticators: starting authenticators
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Idle to PamAuthenticators::Authenticating
kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Starting authentication
kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication
kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Starting authentication
kscreenlocker_greet: [PAM worker kde-smartcard] Message: Info message: auth=authinfo_unavail
kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Authentication done, result code: 9 (Authentication service cannot retrieve authentication info)
file:///home/nate/kde/usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockOsd.qml:10:1: "../osd": no such directory
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-fingerprint true
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-smartcard true
kscreenlocker_greet: PamAuthenticators: Info message from non-interactive authenticator kde-smartcard
kscreenlocker_greet: PamAuthenticators: Delay started on login failure for non-interactive authenticator kde-smartcard duration: 0
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-smartcard false
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-smartcard false
kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password: 
kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await response
kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive authenticator kde
kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Authentication done, result code: 9 (Authentication service cannot retrieve authentication info)
kscreenlocker_greet: PamAuthenticators: Delay started on login failure for non-interactive authenticator kde-fingerprint duration: 0
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-fingerprint false
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-fingerprint false
kscreenlocker_greet: PamAuthenticators: cancelling interactive authenticator
kscreenlocker_greet: [PAM worker kde] Received cancellation, exiting with PAM_CONV_ERR
kscreenlocker_greet: [PAM worker kde] Nested event loop's exit code was not zero, bailing
kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password: 
kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await response
kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive authenticator kde
kscreenlocker_greet: PamAuthenticators: responding to interactive authenticator
kscreenlocker_greet: [PAM worker kde] Received response, exiting nested event loop
kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde changed business
kscreenlocker_greet: PamAuthenticators: Delay started on login failure for interactive authenticator kde duration: 1748302
kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done, result code: 7 (Authentication failure)
kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde changed business
kscreenlocker_greet: PamAuthenticators: Failure from interactive authenticator kde



$ cat /etc/pam.d/kde
auth        substack      password-auth
auth        include       postlogin

account     required      pam_nologin.so
account     include       password-auth

password    include       password-auth

session     required      pam_selinux.so close
session     required      pam_loginuid.so
session     required      pam_selinux.so open
session     optional      pam_keyinit.so force revoke
session     required      pam_namespace.so
session     include       password-auth
session     include       postlogin



$ sudo faillock --user $USER
[sudo] password for nate: 
nate:
When                Type  Source                                           Valid

*** Bug 513476 has been marked as a duplicate of this bug. ***

I am also experiencing this bug, on both Wayland and X11, with both the "Sleep" button and the "Hibernate" button on the lock screen.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.6.1
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.18.13-arch1-1 (64-bit)
Graphics Platform: X11 and Wayland

I believe I am encountering this issue.

Here's my system details:
Operating System: CachyOS Linux 
KDE Plasma Version: 6.7.2
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.1.3-2-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen AI 9 HX 370 w/ Radeon 890M
Memory: 32 GiB of RAM (30.6 GiB usable)
Graphics Processor: AMD Radeon 890M Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen AI 300 Series)
System Version: A9

I do have the fingerprint reader set up and use it regularly to unlock (mentioning just in case it matters).

There is no "kde" under /etc/pam.d/ on my system.

I am able to reproduce the issue consistently using the steps below. I did these steps after running the kscreenlocker_greet testing command from David Edmundson's earlier comment.
1. Clicked on Sleep
2. Pressed power button to wake
3. Clicked on Sleep
4. Pressed power button to wake
    - "Unlocking failed" was briefly displayed, then the whole prompt disappeared and the background un-blurred
5. Wiggled mouse to bring back the prompt
    - The prompt was displayed with the warning message "The account is locked due to 3 failed logins. (10 minutes left to unlock)"
6. Entered password
    - Password was rejected; the warning message persisted
7. Switched to another tty, ran `faillock --user breser --reset` as root, and switched back
8. Entered password
    - The warning message did the rejection shake, then disappeared, leaving behind a clean prompt
9. Entered password
    - The warning message came back and persisted
10. Entered password
    - The warning message did the rejection shake, then disappeared, leaving behind a clean prompt
11. Entered password
    - Computer unlocked

Here's the whole terminal output:

```
~  
❯ export QT_LOGGING_RULES='kscreenlocker_greet.debug=true'  
  
~  
❯ /usr/lib/kscreenlocker_greet --testing  
kscreenlocker_greet: Greeter is starting up.  
kscreenlocker_greet: [PAM worker kde] start: successfully started  
kscreenlocker_greet: [PAM worker kde-fingerprint] start: successfully started  
kscreenlocker_greet: [PAM worker kde-smartcard] start: successfully started  
kscreenlocker_greet: Greeter is running in testing mode  
kscreenlocker_greet: Testing mode enabled: true  
Locked at 1783999728  
kscreenlocker_greet: PamAuthenticators: starting authenticators  
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Idle to PamAuthenticators::Authenticating  
kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication  
kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Starting authentication  
kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Starting authentication  
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-fingerprint true  
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-smartcard true  
kscreenlocker_greet: [PAM worker kde-smartcard] Authenticate: Authentication done, result code: 28 (Module is unknown)  
kscreenlocker_greet: PamAuthenticators: Delay started on login failure for non-interactive authenticator kde-smartcard duration: 2333552  
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-smartcard false  
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-smartcard false  
kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password:    
kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await response  
kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive authenticator kde  
kscreenlocker_greet: [PAM worker kde-fingerprint] Message: Info message: Place your finger on the fingerprint reader  
kscreenlocker_greet: PamAuthenticators: Info message from non-interactive authenticator kde-fingerprint  
kscreenlocker_greet: PamAuthenticators: cancelling interactive authenticator  
kscreenlocker_greet: [PAM worker kde] Received cancellation, exiting with PAM_CONV_ERR  
kscreenlocker_greet: [PAM worker kde] Nested event loop's exit code was not zero, bailing  
kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done, result code: 20 (Authentication token manipulation error)  
kscreenlocker_greet: PamAuthenticators: Delay started on login failure for interactive authenticator kde duration: 1806636  
kscreenlocker_greet: PamAuthenticators: Failure from interactive authenticator kde  
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Authenticating to PamAuthenticators::Idle  
kscreenlocker_greet: [PAM worker kde-fingerprint] Authenticate: Authentication done, result code: 9 (Authentication service cannot retrieve authentication info)  
kscreenlocker_greet: PamAuthenticators: Delay started on login failure for non-interactive authenticator kde-fingerprint duration: 2063284  
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-fingerprint false  
kscreenlocker_greet: PamAuthenticators: Availability changed for non-interactive authenticator kde-fingerprint false  
kscreenlocker_greet: PamAuthenticators: starting authenticators  
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Idle to PamAuthenticators::Authenticating  
kscreenlocker_greet: [PAM worker kde] Authentication attempt too soon. This shouldn't happen!  
kscreenlocker_greet: PamAuthenticators: Failure from interactive authenticator kde  
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Authenticating to PamAuthenticators::Idle  
kscreenlocker_greet: PamAuthenticators: cancelling interactive authenticator  
kscreenlocker_greet: PamAuthenticators: starting authenticators  
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Idle to PamAuthenticators::Authenticating  
kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication  
kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password:    
kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await response  
kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive authenticator kde  
kscreenlocker_greet: PamAuthenticators: cancelling interactive authenticator  
kscreenlocker_greet: [PAM worker kde] Received cancellation, exiting with PAM_CONV_ERR  
kscreenlocker_greet: [PAM worker kde] Nested event loop's exit code was not zero, bailing  
kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done, result code: 20 (Authentication token manipulation error)  
kscreenlocker_greet: PamAuthenticators: Delay started on login failure for interactive authenticator kde duration: 1677028  
kscreenlocker_greet: PamAuthenticators: Failure from interactive authenticator kde  
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Authenticating to PamAuthenticators::Idle  
kscreenlocker_greet: PamAuthenticators: cancelling interactive authenticator  
kscreenlocker_greet: PamAuthenticators: starting authenticators  
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Idle to PamAuthenticators::Authenticating  
kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication  
kscreenlocker_greet: [PAM worker kde] Message: Info message: The account is locked due to 3 failed logins.  
kscreenlocker_greet: [PAM worker kde] Message: Info message: (10 minutes left to unlock)  
kscreenlocker_greet: PamAuthenticators: Info message from interactive authenticator kde  
kscreenlocker_greet: PamAuthenticators: Info message from interactive authenticator kde  
kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password:    
kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await response  
kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive authenticator kde  
kscreenlocker_greet: PamAuthenticators: responding to interactive authenticator  
kscreenlocker_greet: [PAM worker kde] Received response, exiting nested event loop  
kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde changed business  
kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done, result code: 7 (Authentication failure)  
kscreenlocker_greet: PamAuthenticators: Delay started on login failure for interactive authenticator kde duration: 1510871  
kscreenlocker_greet: PamAuthenticators: Failure from interactive authenticator kde  
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Authenticating to PamAuthenticators::Idle  
kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde changed business  
kscreenlocker_greet: PamAuthenticators: starting authenticators  
kscreenlocker_greet: PamAuthenticators: state changing from PamAuthenticators::Idle to PamAuthenticators::Authenticating  
kscreenlocker_greet: [PAM worker kde] Authenticate: Starting authentication  
kscreenlocker_greet: [PAM worker kde] Message: Echo-off prompt: Password:    
kscreenlocker_greet: [PAM worker kde] Starting nested event loop to await response  
kscreenlocker_greet: PamAuthenticators: Secret prompt from interactive authenticator kde  
kscreenlocker_greet: PamAuthenticators: responding to interactive authenticator  
kscreenlocker_greet: [PAM worker kde] Received response, exiting nested event loop  
kscreenlocker_greet: PamAuthenticators: Interactive authenticator kde changed business  
kscreenlocker_greet: [PAM worker] Fail delay function was called, but authentication result was a success!  
kscreenlocker_greet: [PAM worker kde] Authenticate: Authentication done, result code: 0 (Success)  
kscreenlocker_greet: PamAuthenticators: Success from interactive authenticator kde  
Unlocked

~ 1m 38s
❯ faillock --user $USER
breser:
When                Type  Source                                           Valid

```

*** Bug 523332 has been marked as a duplicate of this bug. ***

*** Bug 490924 has been marked as a duplicate of this bug. ***

*** Bug 522806 has been marked as a duplicate of this bug. ***

My symptoms don't match this much at all, but the bug that did match them better was duped to here, so here's what I've got:

1. Select Sleep from Kicker/kickoff/whatever menu
2. Laptop sleeps
3. Wake laptop
4. Immediately: Earthquake, "Unlocking failed", short timeout
5. After timeout, log back in as normal

Every time. First or multiple sleeps after cold boot, doesn't matter. (Not tried sleeping from locked because I don't ever do that. Can do if it's deemed useful to check.) Started happening *only* after upgrade plasma-6.4.4 -> 6.7.2.

But if y'all are adamant this belongs here as well, fine by me.

Info:
Operating System: Gentoo Linux 
KDE Plasma Version: 6.7.2
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.1.1-gentoo (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i7-7600U CPU @ 2.80GHz
Memory: 16 GiB of RAM (15.4 GiB usable)
Graphics Processor: Intel® HD Graphics 620
Init: OpenRC

Oh boy, I think you hit a *combination* of this bug and Bug 510992. To verify if it's the same bug, can you try running in a terminal:

echo 1 > /sys/power/pm_print_times
echo 1 > /sys/power/pm_debug_messages
(try sleeping your system)
journalctl --system -b0 (then press the End key on your keyboard and scroll around looking for interesting log messages)?

Sorry, if "wake laptop" means you manually woke it and not by itself, I probably interpreted your comment wrong.

(In reply to nyanpasu64 from comment #31)
> Sorry, if "wake laptop" means you manually woke it and not by itself, I
> probably interpreted your comment wrong.

That is indeed what I meant. Got 99 problems but an insomniac laptop ain't one (to date).