Logging into the greeter fails often

[senntore]

Usually I'm able to log-in but sometimes the greeter doesn't seem to work as expected.
I don't get the error message(below) in all of those occasions but I did got it once.
unable to send message: Transport endpoint is not connected (os error 107)

Let me know if anything on my end would fix this for me.

[jamestait]

This sounds similar to an issue I'm experiencing. The error message is not exactly the same, but it sounds like it might be affecting the greeter in the same way. I get unable to send message: Connection refused (os error 111). I'm not sure when this started, because I've just rebooted for the first time since probably before Christmas.

Restoring gdm3 as the display manager with sudo dpkg-reconfigure gdm3 has allowed me to log in again; prior to that I was worried it was something to do with my somewhat esoteric setup, which started life as a standard Ubuntu installation some 10 or so years ago and has probably accumulated some cruft.

Another item I think I've ruled out is my use of sssd for LDAP-based single sign-on: reconfiguring PAM to exclude SSS authentication via sudo pam-auth-update did not resolve the issue.

What's the best way for me to provide system configuration info and debug logs to help resolve this?

[aschiavon91]

I'm also receiving unable to send message: Connection refused (os error 111) after trying to login, but in my case, I have pam-fprint configured.

[jamestait]

I did a little digging with strace and was able to see the conversation between greeterd and (presumably) the SSS PAM module/backend; I realised that a character in my password was incorrect, and recognised the incorrectness as being due to an incorrect keyboard mapping: US QWERTY instead of UK QWERTY. So I was able to login with the necessary correction, although on the successful attempt I didn't observe the conversation as I has before. This matched the behaviour under gdm3, so it could be that it's using the locally-cached credential DB in that instance.

I'll keep poking it to see if I can narrow it down further, but I'm groping in the dark a little bit because I'm not quite sure of the order the different processes are invoked and how the messaging works between them -- and in an attempt to avoid caching, I'll probably need to reboot between each attempt.

[jackpot51]

#54 may have improved this.

[senntore]

I tested it multiple times and it seems to work.
Now it fail only when trying to log in to a Pop wayland session(x-org seems to work).
But since we won't have a gnome(wayland) session by default in the alpha, I imagine it's okay to close this for now.
Feel free to close this issue.

[jackpot51]

Thanks for testing. I will work on the GNOME Wayland issue in #18

[WatchMkr]

This problem still occurs on my darp8. This report could be helpful: #56