lightdm login loop with systemd-homed
It seems that from systemd 256 onwards, lightdm cannot properly log into homed user accounts. At least in X sessions. It keeps in a loop of "getting password --> (trying to) logging in --> black journaled screen --> getting back to the first step asking for password again" It can't read ~/.Xauthority, tries to find it at /.Xauthority instead. lightdm unit logs says: ~~~ Error writing X authority: Failed to open X authority /.Xauthority: Permission denied ~~~ It doesn't seem to be related to https://wiki.archlinux.org/title/LightDM#Infinite_login_loop Also, there's an open issue related to this in lightdm's github repository Is there anyone who is experiencing the same issue? -- Best Regards, Abraham Sent with Tutanota; https://tuta.com
On 11.09.24 13:30, Abraham S.A.H. wrote:
It seems that from systemd 256 onwards, lightdm cannot properly log into homed user accounts. At least in X sessions.
It keeps in a loop of "getting password --> (trying to) logging in --> black journaled screen --> getting back to the first step asking for password again"
It can't read ~/.Xauthority, tries to find it at /.Xauthority instead.
lightdm unit logs says: ~~~ Error writing X authority: Failed to open X authority /.Xauthority: Permission denied ~~~
It doesn't seem to be related tohttps://wiki.archlinux.org/title/LightDM#Infinite_login_loop
Also, there's an open issue related to this in lightdm's github repository
Is there anyone who is experiencing the same issue?
Hi Abnraham, maybe we share the same problem. Try to switch to a text console (e.g. CTRL+ALT+F4) and login as the desired user. Switch back to lightdm (ALT+F7) and try to login. That works for me. -- Gruß Michael Gisbers http://gisbers.de Matrix: @mgisbers:matrix.dynlinux.io GnuPG Fingerprint: DD12 A30E 5070 68C7 B405 C18E D51C 8A53 63B4 835B GnuPG PublicKey:https://tinyuri.de/mgisberspub https://keybase.io/mgisbers
maybe we share the same problem.
We do.
Try to switch to a text console (e.g. CTRL+ALT+F4) and login as the desired user. Switch back to lightdm (ALT+F7) and try to login.
Was doing that all along since the issue arose.
That works for me.
Currently, sounds like the only workaround. --- End
Hey, I don't know why, but manually entering the username instead of choosing the ready username of the user on the Lightdm's login screen solves the problem. -- Best Regards, Abraham Sent with Tutanota; https://tuta.com
On 9/24/24 11:27 AM, Abraham S.A.H. wrote:
Hey,
I don't know why, but manually entering the username instead of choosing the ready username of the user on the Lightdm's login screen solves the problem.
A similar issue with TDE was seen with both kdm and lightdm that Felix Miata chased down to the fact that dbus.socket was not starting dbus-broker.service. https://bugzilla.opensuse.org/show_bug.cgi?id=1229813 That may have some information that helps (may not, but appeared similar enough) -- David C. Rankin, J.D.,P.E.
Yes, they appear to be similar, but they are still different issues. This topic's issue is about a user failing to login on display manger (LightDM in this case), specially with a systemd-homed encrypted home. But that issue is related to failing to boot and ending up in emergency mode. -- Best Regards, Abraham Sent with Tutanota; https://tuta.com
A similar issue with TDE was seen with both kdm and lightdm
By the way, do you use TDE? If yes, how is it? Would you suggest it? I love DE hopping. :) -- Best Regards, Abraham Sent with Tutanota; https://tuta.com
participants (3)
-
Abraham S.A.H.
-
David C. Rankin
-
Michael Gisbers