Can't auto login after upgrading to 2.3.1-3ubuntu4 on 20.10

Thanks for taking the time to file this bug.

While checking the logs I noticed this:

Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: Loaded settings from: /usr/lib/realmd/realmd-defaults.conf /usr/lib/realmd/realmd-distro.conf
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: holding daemon: startup
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: starting service
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: connected to bus
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: GLib-GIO: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: released daemon: startup
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: claimed name on bus: org.freedesktop.realmd
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: client using service: :1.115
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: holding daemon: :1.115
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: * Resolving: _ldap._tcp.taipei
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: * Resolving: _ldap._tcp.taipei
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: Resolving taipei failed: No DNS record of the requested type for “_kerberos._udp.taipei”
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: No DNS record of the requested type for “_ldap._tcp.taipei”
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: * Resolving: taipei
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: * Resolving: taipei
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: Error resolving “taipei”: Temporary failure in name resolution
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: * No results: taipei
Mar 4 01:49:13 precision-3551-c3x-202002-27718 realmd[2210]: * No results: taipei

Which makes me believe this is a DNS issue. Could share your sssd conf to help us understand your setup? And possibly reproduce the bug locally. FWIW I am subscribing Sergio who has been working on sssd recently.

Thanks for the bug report, Kevin.

I followed your instructions on how to reproduce it, but failed. The auto-login feature is working in my pristine Groovy VM even after I fully upgrade the system and install sssd.

What Lucas pointed above is indeed strange: you could be facing some unrelated issue (like DNS) that might be affecting how your system behaves. For example, it seems like there is some sort of LDAP-based authentication that you're trying to use, maybe?

Other things that caught my attention in the logs:

1) I could not find any mention to sssd.service whatsoever in your journalctl.log.

2) You seem to be using a system that has been configured before. Based on the instructions you posted in the bug description explaining how to reproduce the issue, I was under the impression that the problem happened after a pristine installation of Ubuntu Groovy.

Having said all that, I would like to reinforce Lucas's request and ask you to provide your sssd configuration file so that we can try to reproduce the issue here. Also, please try to mention everything that might affect the authentication process, like the use of LDAP servers, AD, etc.

Because I could not reproduce the bug locally, I am marking it as Incomplete. When you provide the necessary information, feel free to mark the bug as New again.

Thanks.

[Expired for sssd (Ubuntu) because there has been no activity for 60 days.]