gnome-initial-setup-46.alpha-4.fc40 fails to hand off to a desktop when creating a user
gnome-initial-setup-46.alpha-4.fc40 is failing tests in Fedora (-3.fc40 did, too). On first boot of a fresh install, after you complete g-i-s, it should hand off to a logged-in desktop as the user you just created - but it doesn't. The system winds up just stuck in the sort of half-complete desktop used to run g-i-s.
In the journal, we see this:
Jan 18 05:57:55 fedora accounts-daemon[750]: request by system-bus-name::1.77 [/usr/libexec/gnome-initial-setup pid:1494 uid:977]: create user 'test'
Jan 18 05:57:55 fedora useradd[1839]: new group: name=test, GID=1000
Jan 18 05:57:55 fedora useradd[1839]: new user: name=test, UID=1000, GID=1000, home=/home/test, shell=/bin/bash, from=none
Jan 18 05:57:55 fedora useradd[1839]: add 'test' to group 'wheel'
Jan 18 05:57:55 fedora useradd[1839]: add 'test' to shadow group 'wheel'
Jan 18 05:57:55 fedora accounts-daemon[1842]: [sss_cache] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb]
Jan 18 05:57:55 fedora accounts-daemon[1842]: Could not open available domains
Jan 18 05:57:55 fedora useradd[1839]: useradd: sss_cache exited with status 5
Jan 18 05:57:55 fedora useradd[1839]: useradd: Failed to flush the sssd cache.
Jan 18 05:57:55 fedora accounts-daemon[1845]: [sss_cache] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb]
Jan 18 05:57:55 fedora accounts-daemon[1845]: Could not open available domains
Jan 18 05:57:55 fedora useradd[1839]: useradd: sss_cache exited with status 5
Jan 18 05:57:55 fedora useradd[1839]: useradd: Failed to flush the sssd cache.
Jan 18 05:57:55 fedora accounts-daemon[750]: request by system-bus-name::1.77 [/usr/libexec/gnome-initial-setup pid:1494 uid:977]: set password and hint of user 'test' (1000)
Jan 18 05:57:55 fedora accounts-daemon[1855]: [sss_cache] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb]
Jan 18 05:57:55 fedora accounts-daemon[1855]: Could not open available domains
Jan 18 05:57:55 fedora chpasswd[1851]: chpasswd: sss_cache exited with status 5
Jan 18 05:57:55 fedora chpasswd[1851]: chpasswd: Failed to flush the sssd cache.
Jan 18 05:57:56 fedora accounts-daemon[1857]: [sss_cache] [confdb_init] (0x0010): Unable to open config database [/var/lib/sss/db/config.ldb]
Jan 18 05:57:56 fedora accounts-daemon[1857]: Could not open available domains
Jan 18 05:57:56 fedora chpasswd[1851]: chpasswd: sss_cache exited with status 5
Jan 18 05:57:56 fedora chpasswd[1851]: chpasswd: Failed to flush the sssd cache.
Jan 18 05:57:56 fedora gnome-initial-s[1494]: Unable to save state to /var/lib/gnome-initial-setup/state: Failed to create file “/var/lib/gnome-initial-setup/state.CSVRH2”: Permission denied
Jan 18 05:57:56 fedora gnome-initial-s[1494]: act_user_get_uid: assertion 'ACT_IS_USER (user)' failed
Jan 18 05:57:56 fedora gnome-initial-s[1494]: act_user_get_user_name: assertion 'ACT_IS_USER (user)' failed
Jan 18 05:57:56 fedora gnome-initial-s[1494]: g_variant_new_string: assertion 'string != NULL' failed
Jan 18 05:57:56 fedora gdm-password][1858]: accountsservice: ActUserManager: user (null) has no username (uid: -1)
The user account is actually created; if you reboot, you wind up at a GDM screen where the user is available for login, and login works. I don't know if anything is "missing" from the account due to this bug.
As this has a couple of critical errors in it, @mcatanzaro wanted me to try with G_DEBUG=fatal-criticals
. I had to do quite a bit of fiddling about to get that applied to the g-i-s environment and get it to actually produce a coredump: rebuild gdm to set that env var in the env it runs g-i-s in, then use prlimit
to override the core size limit of the g-i-s process (it seems to be 0 by default, whatever /etc/security/limits.conf
says), and then actually get all the way through g-i-s without fatal-criticals causing anything else to crash. But I got there! This is the backtrace.