https://bugs.kde.org/show_bug.cgi?id=490924
Alex Sanchez-Stern <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #35 from Alex Sanchez-Stern <[email protected]> --- I hit this issue (or at least a related issue) on Arch with a plain pam_unix stack (no SSSD, no fingerprint/smartcard hardware). The visible symptom on my end is the lock screen showing a failed attempt on wake, without me ever having typed anything. But as far as I can tell its the same root cause event from here: m_authenticator->cancel() on suspend leading to a PAM_CONV_ERR. It looks like pre-6.7, this could only happen when you hit the sleep/suspend button on the lock screen, sending the cancel. But as of the 6.7.0 release (specifically 9e622c8676fa), some of the "suspend from lid close" logic was merged into the same sleep/suspend button logic, so closing the lid while the password prompt is up sends the PAM cancel, which gets mis-classified as a failed password attempt, causing the failed login attempt and delay before another password attempt. This, I believe, makes this bad behavior *much* more common; on some laptops just being jostled around can cause lid open and close events in rapid succession, triggering the bug on the first real wake. MR 240 doesn't appear to actually fix the issue, because in my case PAM_CONV_ERR *is* already being returned, but the problem is that it doesn't get handled any differently than a password failure, hence the password failure. The fix should be to add a special path for cancelled authentication attempts as opposed to failed ones. -- You are receiving this mail because: You are watching all bug changes.
