| Summary: | Authentication failure is triggered immediately after resume before any password is entered | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | adhikaridipendu |
| Component: | Screen locking | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.7.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | output of "sudo journalctl --no-pager --since "2026-06-29 19:22:35" --until "2026-06-29 21:46:08" > kde_error.log" | ||
*** This bug has been marked as a duplicate of bug 521900 *** |
Created attachment 193856 [details] output of "sudo journalctl --no-pager --since "2026-06-29 19:22:35" --until "2026-06-29 21:46:08" > kde_error.log" After resuming from suspend on Plasma Wayland session the lock screen immediately triggers an authentication failure before any password has been entered. error flow- boot into plasma wayland session login let the system stay idle for sometime to auto lock wake up the system by any means (touching the touchpad or mocing mouse) do not type the password result an authentication failure is triggered before any user input saying could not authenticate* the journal contained pam_unix(kde:auth): unexpected response from failed conversation function conversation failed auth could not identify password for [username] pacman -Q kscreenlocker plasma-workspace kwin plasma-desktop linux linux-firmware qt6-base kscreenlocker 6.7.1-1 plasma-workspace 6.7.1-1 kwin 6.7.1-1 plasma-desktop 6.7.1-1 linux 7.0.14.arch1-1 linux-firmware 20260622-1 qt6-base 6.11.1-1 echo $XDG_SESSION_TYPE wayland plasmashell --version plasmashell 6.7.1 kwin_wayland --version kwin 6.7.1 uname -a Linux [ ] 7.0.14-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 27 Jun 2026 16:15:10 +0000 x86_64 GNU/Linux kded6 --version kded6 6.27.0 this issue has been going on lately for sometimes now with the exact same error and exact same condition