SUMMARY When I put the computer to sleep from a lock screen, I see that before the screen goes black, the password field behaves as if I tried unlocking with a wrong password. STEPS TO REPRODUCE 1. Lock the screen (e.g. Meta+L) 2. Click “Sleep” OBSERVED RESULT The password field is greyed out, a message about an invalid password is displayed, then the computer sleeps. EXPECTED RESULT The computer goes to sleep without password drama :) SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20240223 KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.7.5-1-default (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION
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