| Summary: | KScreen locker does not play nice with systemd-homed | ||
|---|---|---|---|
| Product: | [Unmaintained] kscreenlocker | Reporter: | Matthew <mattjs> |
| Component: | kcheckpass | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | bshah, demm, kde, klaussemmler, mattjs |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | my kscreenlocker test results and two pam files rolled into one because i can't submit multiple files | ||
I cannot reproduce this issue with Arch Linux. I installed the system with zen-installer and created a user with systemd-homed. I can unlock the lockscreen like always kscreenlocker goes through PAM correctly. Anything else is a downstream issue, unless shown otherwise. I would suggest you start by checking those are the correct pam files, by default kscreenlocker uses /etc/pam.d/kde which then includes some other auth files, but it gets very distro-dependent. You are correct, it does work fine now. Not sure what it was that was giving me an issue before but it seems to be resolved now. Thank you! |
Created attachment 129927 [details] my kscreenlocker test results and two pam files rolled into one because i can't submit multiple files SUMMARY When using systemd-homed, I cannot log into my machine after it is locked with kscreenlocker. SDDM greeter seems to work okay, although not perfectly. SDDM freezes on loading if I try to switch users to myself after a failed unlock from kscreenlocker. In general kde/plasma does not recognize my user. I had to edit PAM to get it to work at all. changed/added PAM files are include, which may have issues of their own as i am unfamiliar with PAM. I don't get any errors from sddm or systemd-homed in journalctl when I run i have attached the output of kscreenlocker_greet --testing. STEPS TO REPRODUCE 1. install os, do not create a user (this step could probably be skipped) 2. enable systemd-homed 3. create user using homectl 4. edit PAM to allow sddm to even attempt logging in 5. log in 6. lock screen 7. try to unlock screen OBSERVED RESULT gets an "unlock failed" response EXPECTED RESULT session unlocks properly SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux kernel 5.7 KDE Plasma Version: kde plasma 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION running manjaro with systemd-homed enabled and in use. os installed with manjaro using manjaro architect with the minimal kde package