Autologin with user with expired password results in GDM not showing up
Debian sid/unstable with gdm 3.38.2.1-1. Plymouth is not installed.
Debian sid/unstable has some password policy change, that passwords expire, and users have to update it on the next login. At least with autologin enabled, this results in GDM not showing up. On tty1 only the startup messages (from Linux and systemd) are shown, and the user thinks the system froze.
$ journalctl -b -u gdm
-- Journal begins at Tue 2021-02-09 14:30:21 CET, ends at Tue 2021-08-24 15:37:57 CEST. --
Aug 24 15:26:20 tokeiihto systemd[1]: gdm.service: Watching D-Bus name 'org.gnome.DisplayManager'.
Aug 24 15:26:20 tokeiihto systemd[1]: gdm.service: starting held back, waiting for: systemd-user-sessions.service
Aug 24 15:26:20 tokeiihto systemd[1]: gdm.service: D-Bus name org.gnome.DisplayManager now not owned by anyone.
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: About to execute /usr/share/gdm/generate-config
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Forked /usr/share/gdm/generate-config as 430
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Changed dead -> start-pre
Aug 24 15:26:21 tokeiihto systemd[1]: Starting GNOME Display Manager...
Aug 24 15:26:21 tokeiihto systemd[430]: gdm.service: Executing: /usr/share/gdm/generate-config
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Child 430 belongs to gdm.service.
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Control process exited, code=exited, status=0/SUCCESS
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Got final SIGCHLD for state start-pre.
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Passing 0 fds to service
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: About to execute /usr/sbin/gdm3
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Forked /usr/sbin/gdm3 as 433
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Changed start-pre -> start
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Control group is empty.
Aug 24 15:26:21 tokeiihto systemd[433]: gdm.service: Executing: /usr/sbin/gdm3
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: D-Bus name org.gnome.DisplayManager now owned by :1.8
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Changed start -> running
Aug 24 15:26:21 tokeiihto systemd[1]: gdm.service: Job 110 gdm.service/start finished, result=done
Aug 24 15:26:21 tokeiihto systemd[1]: Started GNOME Display Manager.
Aug 24 15:26:21 tokeiihto gdm-autologin][439]: gkr-pam: no password is available for user
Aug 24 15:26:21 tokeiihto gdm-autologin][439]: pam_unix(gdm-autologin:account): expired password for user joey (root enforced)
Aug 24 15:26:21 tokeiihto gdm3[433]: Gdm: gdm_session_handle_secret_info_query: assertion 'self->user_verifier_interface != NULL' failed
Aug 24 15:26:21 tokeiihto gdm-autologin][439]: pam_unix(gdm-autologin:chauthtok): conversation failed
Aug 24 15:26:21 tokeiihto gdm-autologin][439]: pam_unix(gdm-autologin:chauthtok): password - (old) token not obtained
Switching to tty2, logging in there and changing/updating the password works around it.
I would have expected at least the GDM login screen to be started instead.