As I also can't login through lightdm right now, I tried to follow this
recipe as well. Merely removing .ICEauthority and .Xauthority doesn't
seem to be sufficient for me; may it be that this is just a red herring,
and that logging into the VT is a required step here to unlock ecryptfs?
What I did notice is that lightdm defaults to the wrong user for me (my
"joe" test user), and already starts a PAM session for joe right at
startup:
[+20.82s] DEBUG: Greeter start authentication for joe
[+20.82s] DEBUG: pam_start("lightdm", "joe") -> (0x7f8a440248f0, 0)
Changing to "martin" and trying to log in fails, I just get a black
screen quickly, and then returns to lightdm. It does work if I switch
between some more users, and then back to "martin". I need to examine
this more closely, might very well be totally unrelated to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/823775
Title:
Cannot login: could not update ICEauthority file .ICEauthority
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/823775/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
