I'm unable to login to SDDM when using an account created by systemd-homed. Initially the user was invisible. I resolved this, by changing the MaxGuid and MinGuid parameters in SDDM. After whenever I try to login, SDDM flashes twice and just goes back to the main page. Logging in via the CLI works fine. I have the homed USE flag set (and thus enabled in pambase). - I've tried to create a user using useradd and reverting back the MinGuid and MaxGuid and when creating the user using useradd, I'm able to log in just fine. So it's not the user account. Reproducible: Always Steps to Reproduce: 1.Create an account using homectl (used luks as storage-type) 2.Adjust MinGuid and MaxGuid conforming systemd-homed 3.Start SDDM and login with the specified accounts Actual Results: I get redirected back to the main screen Expected Results: A logged in user Please let me know what additional information is needed
CCing pambase maintainers in case it's our fault / systemd maintainers.
After re-compiling all related packages on my system, it's logging in, but only if I type the password correctly the first time. - If I make a typo and try to login, it won't login anymore, having to reboot my computer or switch to the CLI. - In rare cases I'm unable to login to SDDM on boot as well (even with the password typed correctly), where it does not display any message and just sits there, allowing me to type in the password and press enter or click on the arrow, but nothing happens. No message, no response nothing. Is there any additional information you guys need? Please let me know if you do. I'll attach my emerge --info as that's the least I can do.
Created attachment 799057 [details] emerge --info