Bug 461326

Summary:	Cannot unlock after locking screen (unlock failed, user unknown in logs)
Product:	[Plasma] kscreenlocker	Reporter:	kim <stylinsonnelly>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	critical	CC:	bhush94, kde, kde, nate
Priority:	VHI
Version:	5.26.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description kim 2022-11-02 17:36:04 UTC

SUMMARY
When I start my laptop and log in, everything is fine. When I lock manually (meta + L) or my screen locks automatically, I can't log back to system. All I get is Unlock failed. When I switch to another tty I'm able to log in in root and my user. Journalctl gives me 'check pass; user unknown' when I try to unlock screen with sddm. But, when I try to unlock my screen with KDE Connect on iOS, it unlocks. It started as a random appearing problem, but now I am able to reproduce it any time i lock the screen.

STEPS TO REPRODUCE
1. Lock screen by using shortcut/menu/automatically (after a period of time)
2. Try to unlock the screen with correct password to user
3. Unlocking failed with correct password
4. After several retries, I get faillock

OBSERVED RESULT
I get Unlock failed every time. Also, after 3 retries i get pam faillock. Unlocking with KDE Connect is working correctly, I am able to use my system.

EXPECTED RESULT
I can unlock my screen with SDDM.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.26.2
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.7
Kernel Version: 6.0.6-arch1-1 (64-bit)
KDE Connect for iOS version: 0.2.1 (2)

Comment 1 Nate Graham 2022-11-02 18:48:09 UTC

Some questions:
1. How many screens do you have?
2. Are you using fingerprint auth?
3. Are you using any unusual or non-default PAM settings/configs/etc?

Comment 2 kim 2022-11-02 18:51:10 UTC

(In reply to Nate Graham from comment #1)
> Some questions:
> 1. How many screens do you have?
> 2. Are you using fingerprint auth?
> 3. Are you using any unusual or non-default PAM settings/configs/etc?

1. Only 1 screen (laptop)
2. No, only password (I have built-in fingerprint scanner but I haven't configured it)
3. No, I haven't touched these configs, they're default.

Comment 3 kim 2022-11-02 18:57:57 UTC

Also, this happens for me even when I try kscreenlocker_greet --testing

Comment 4 Nate Graham 2022-11-02 19:07:11 UTC

Oh dear, that's bad.

Can you paste the output in your terminal window when you click on the "Unlock" button while running kscreenlocker_greet? That would be helpful, thanks!

Comment 5 kim 2022-11-02 19:40:15 UTC

(In reply to Nate Graham from comment #4)
> Oh dear, that's bad.
> 
> Can you paste the output in your terminal window when you click on the
> "Unlock" button while running kscreenlocker_greet? That would be helpful,
> thanks!

i get this in terminal. tried with my theme (materia) and with setting default breeze theme, it has nothing to do with theme (i hope)
$ /usr/lib/kscreenlocker_greet --testing                                            
file:///usr/share/plasma/look-and-feel/com.github.varlesh.materia-dark/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
Locked at 1667417697
qt.gui.icc: fromIccProfile: failed minimal tag size sanity

Comment 6 Nate Graham 2022-11-04 16:16:43 UTC

Thanks. Does it help to install the Qt Virtual Keyboard module package, or does it make no difference?

Comment 7 kim 2022-11-04 16:29:29 UTC

(In reply to Nate Graham from comment #6)
> Thanks. Does it help to install the Qt Virtual Keyboard module package, or
> does it make no difference?
No, still Unlock failed.

Locked at 1667579030
qt.gui.icc: fromIccProfile: failed minimal tag size sanity
qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_US" . Search paths ("/usr/share/qt/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts")

Comment 8 Nate Graham 2022-11-04 16:35:27 UTC

Thanks for the info. That's bad.

Comment 9 Christian (Fuchs) 2022-11-19 11:07:38 UTC

*** Bug 462016 has been marked as a duplicate of this bug. ***

Comment 10 David Edmundson 2022-11-25 11:29:04 UTC


*** This bug has been marked as a duplicate of bug 456210 ***

Comment 11 kim 2022-12-03 20:55:58 UTC

trying to fix this for around 3 months, i tried removing kde and sddm configs, creating new users, removing everything related to kde connect, installing it again, chmod to chkpwd sudo and su, reinstalled plasma, sddm and applications and nothing. everything that works is unlocking with loginctl and kde connect. tried switching to lightdm and then understood that the problem is in the kscreenlocker.