https://bugs.kde.org/show_bug.cgi?id=522307
--- Comment #1 from [email protected] --- UPDATE: Confirmed via Btrfs snapshot comparison on openSUSE Tumbleweed (snapper). Booted into a snapshot taken at 2026-06-27 07:42 (right before pam_kwallet6 was updated from 6.7.0-1.1 to 6.7.1-1.1 on the same machine), with kwalletd6 unchanged at 6.27.0-1.1 in both cases. - With pam_kwallet6 6.7.0: suspend -> resume -> password unlock does NOT trigger the ksecretd CPU loop. Tested across multiple suspend/resume cycles, issue does not reproduce. - With pam_kwallet6 6.7.1 (current): issue reproduces reliably on every suspend/resume + unlock cycle, as originally reported. This strongly points to the regression being introduced specifically in pam_kwallet6 6.7.1 (or its interaction with kwalletd6 6.27.0), rather than in kwalletd6 itself. Might be worth checking the changelog between pam_kwallet6 6.7.0 and 6.7.1 for changes to the screen-unlock ("session" stage / setcred handling) code path. -- You are receiving this mail because: You are watching all bug changes.
