"Failed login attempt" on wake up, before I can even try to log in

Desktop Environments Plasma
1

So when I put my laptop to sleep and wake it up, immediately I get prompted with failed login information, despite the fact that the screen barely turned on and I didn’t have time to make any input.

Here are some logs that I hope will be helpful.

❯ journalctl -b --since “2 minutes ago” | grep -E “kscreenlocker|pam_|faillock|kde:auth” cze 24 15:13:17 Lukasz-Lenovo kscreenlocker_greet[4743]: pam_unix(kde:auth): unexpected response from failed conversation function cze 24 15:13:17 Lukasz-Lenovo kscreenlocker_greet[4743]: pam_unix(kde:auth): conversation failed cze 24 15:13:17 Lukasz-Lenovo kscreenlocker_greet[4743]: pam_unix(kde:auth): auth could not identify password for [lukaszb] cze 24 15:13:19 Lukasz-Lenovo kscreenlocker_greet[4743]: [PAM worker kde] Authentication attempt too soon. This shouldn’t happen!

❯ journalctl -b --since “2 minutes ago” | grep -E “kwin|kscreen|plasma” cze 24 15:12:23 Lukasz-Lenovo plasmashell[1879]: requesting unexisting screen available rect -1 cze 24 15:12:23 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:12:23 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:12:23 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:12:23 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:12:23 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:12:23 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:12:23 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:12:24 Lukasz-Lenovo kernel: WARNING: drivers/gpu/drm/amd/amdgpu/../display/dc/hubbub/dcn31/dcn31_hubbub.c:151 at dcn31_program_compbuf_size+0xd0/0x220 [amdgpu], CPU#15: kwin_wayland/1719 cze 24 15:12:24 Lukasz-Lenovo kernel: CPU: 15 UID: 1000 PID: 1719 Comm: kwin_wayland Tainted: G OE 7.0.12-arch1-1 #1 PREEMPT(full) a172fbca2f7718f1c9472d66b5c7f906f82343b2 cze 24 15:13:17 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:13:17 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:13:17 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:13:17 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:13:17 Lukasz-Lenovo plasmashell[1879]: Final member StackingOrder is overridden in class QQmlDMAbstractItemModelData. The override won’t be used. cze 24 15:13:17 Lukasz-Lenovo plasmashell[1879]: mimeType() not emitted when sending first data!; job URL = QUrl(“https://www.bing.com/HPImageArchive.aspx?format=js&idx=0&n=1”) data size = 0 cze 24 15:13:17 Lukasz-Lenovo kscreenlocker_greet[4743]: pam_unix(kde:auth): unexpected response from failed conversation function cze 24 15:13:17 Lukasz-Lenovo kscreenlocker_greet[4743]: pam_unix(kde:auth): conversation failed cze 24 15:13:17 Lukasz-Lenovo kscreenlocker_greet[4743]: pam_unix(kde:auth): auth could not identify password for [lukaszb] cze 24 15:13:19 Lukasz-Lenovo kscreenlocker_greet[4743]: [PAM worker kde] Authentication attempt too soon. This shouldn’t happen!

❯ loginctl show-session $XDG_SESSION_ID -a | grep -E “State=|LockedHint=|Active=” Active=yes State=active LockedHint=no

2

Could this be related:

3

This has been happening to me too, though I am running Arch Linux and not EndeavourOS.

I’ve pinned point to kscreenlocker_greet which kept doing whatever it is doing and locking me out of my account.

Jul 04 21:40:08 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): unexpected response from failed conversation function
Jul 04 21:40:08 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): conversation failed
Jul 04 21:40:08 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): auth could not identify password for [diskette]
Jul 04 21:40:18 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): unexpected response from failed conversation function
Jul 04 21:40:18 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): conversation failed
Jul 04 21:40:18 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): auth could not identify password for [diskette]
Jul 04 21:40:33 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): unexpected response from failed conversation function
Jul 04 21:40:33 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): conversation failed
Jul 04 21:40:33 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): auth could not identify password for [diskette]
Jul 04 21:47:35 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): unexpected response from failed conversation function
Jul 04 21:47:35 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): conversation failed
Jul 04 21:47:35 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): auth could not identify password for [diskette]
Jul 04 21:51:37 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): unexpected response from failed conversation function
Jul 04 21:51:37 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): conversation failed
Jul 04 21:51:37 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): auth could not identify password for [diskette]
Jul 04 21:51:37 proper kscreenlocker_greet[89936]: pam_faillock(kde:auth): Error sending audit message: Operation not permitted
Jul 04 21:51:47 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): unexpected response from failed conversation function
Jul 04 21:51:47 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): conversation failed
Jul 04 21:51:47 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): auth could not identify password for [diskette]
Jul 04 22:06:14 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): unexpected response from failed conversation function
Jul 04 22:06:14 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): conversation failed
Jul 04 22:06:14 proper kscreenlocker_greet[89936]: pam_unix(kde:auth): auth could not identify password for [diskette]
Jul 04 22:06:14 proper kscreenlocker_greet[89936]: pam_faillock(kde:auth): Error sending audit message: Operation not permitted
Jul 04 22:06:14 proper kscreenlocker_greet[89936]: pam_faillock(kde:auth): Error sending audit message: Operation not permitted
Jul 04 22:06:14 proper kscreenlocker_greet[89936]: pam_faillock(kde:auth): Consecutive login failures for user diskette account temporarily locked

4

This has been happening to me for some time now. It seems to only occur when I wake my laptop up by opening its lid.

journalctl yields, among other messages

set 30 13:27:22 asuszenbook kscreenlocker_greet[15310]: pam_unix(kde:auth): unexpected response from failed conversati
on function
set 30 13:27:22 asuszenbook kscreenlocker_greet[15310]: pam_unix(kde:auth): conversation failed
set 30 13:27:22 asuszenbook kscreenlocker_greet[15310]: pam_unix(kde:auth): auth could not identify password for [user]