Shell doesn't launch after glib 67a589e5
First up this isn't probably the best place for the issue, but its 4am and I've spent about 6 hours bisecting this so I kinda want to dump my findings here and go to bed afterwards.
GNOMEOS stopped being able to start shell sessions today, with a not so helpful log.
Feb 17 22:17:35 slimbook systemd[1]: Startup finished in 3.906s (firmware) + 212ms (loader) + 1.234s (kernel) + 1.159s (initrd) + 21.671s (userspace) = 28.184s.
Feb 17 22:17:41 slimbook gnome-shell[883]: invalid (NULL) pointer instance
Feb 17 22:17:41 slimbook gnome-shell[883]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Feb 17 22:17:44 slimbook systemd[1]: systemd-hostnamed.service: Succeeded.
Feb 17 22:17:45 slimbook mogwai-schedule[565]: Exiting due to reaching inactivity timeout
Feb 17 22:17:45 slimbook systemd[1]: mogwai-scheduled.service: Succeeded.
Feb 17 22:17:50 slimbook wpa_supplicant[574]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-45 noise=9999 txrate=234000
Feb 17 22:17:51 slimbook sshd[1003]: Accepted publickey for alatiera from 192.168.2.2 port 52468 ssh2: ED25519 SHA256:YaPBGBmDs0YrvPTtHiYkuy29vsZSYPaXYDoU5snnDD4
Feb 17 22:17:51 slimbook systemd-logind[571]: New session c1 of user alatiera.
Feb 17 22:17:51 slimbook systemd[1]: Started Session c1 of user alatiera.
Feb 17 22:17:51 slimbook sshd[1003]: pam_unix(ssh:session): session opened for user alatiera(uid=1000) by (uid=0)
Feb 17 22:17:52 slimbook systemd-timesyncd[423]: Initial synchronization to time server 216.239.35.8:123 (time3.google.com).
Feb 17 22:17:57 slimbook wpa_supplicant[574]: wlp1s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-38 noise=9999 txrate=234000
Feb 17 22:18:07 slimbook gnome-shell[883]: JS ERROR: Gio.IOErrorEnum: Error calling StartServiceByName for org.freedesktop.login1: Timeout was reached
_injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25
_makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17
LoginManagerSystemd@resource:///org/gnome/shell/misc/loginManager.js:92:23
getLoginManager@resource:///org/gnome/shell/misc/loginManager.js:82:29
_init@resource:///org/gnome/shell/ui/background.js:252:41
getBackground@resource:///org/gnome/shell/ui/background.js:583:30
_createBackgroundActor@resource:///org/gnome/shell/ui/background.js:748:49
BackgroundManager@resource:///org/gnome/shell/ui/background.js:679:37
_createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:433:25
_updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:477:34
_monitorsChanged@resource:///org/gnome/shell/ui/layout.js:539:14
_init@resource:///org/gnome/shell/ui/layout.js:294:14
_initializeUI@resource:///org/gnome/shell/ui/main.js:203:21
start@resource:///org/gnome/shell/ui/main.js:169:5
@<main>:1:47
Feb 17 22:18:07 slimbook gnome-shell[883]: Execution of main.js threw exception: Script <main> threw an exception
Feb 17 22:18:07 slimbook gnome-shell[979]: could not connect to wayland server
Feb 17 22:18:07 slimbook gnome-shell[979]: (EE)
Feb 17 22:18:07 slimbook gnome-shell[979]: Fatal server error:
Feb 17 22:18:07 slimbook gnome-shell[979]: (EE) Couldn't add screen
Feb 17 22:18:07 slimbook gnome-shell[979]: (EE)
Feb 17 22:18:07 slimbook audit[979]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=kernel pid=979 comm="Xwayland" exe="/usr/bin/Xwayland" sig=6 res=1
Feb 17 22:18:07 slimbook kernel: audit: type=1701 audit(1613593087.222:5): auid=1000 uid=1000 gid=1000 ses=2 subj=kernel pid=979 comm="Xwayland" exe="/usr/bin/Xwayland" sig=6 res=1
Feb 17 22:18:07 slimbook systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Feb 17 22:18:07 slimbook systemd[1]: Started Process Core Dump (PID 1102/UID 0).
Feb 17 22:18:07 slimbook systemd-coredump[1103]: Process 979 (Xwayland) of user 1000 dumped core.
Stack trace of thread 979:
#0 0x00007f4a3a8027f5 __GI_raise (libc.so.6 + 0x397f5)
#1 0x00007f4a3a7eb855 __GI_abort (libc.so.6 + 0x22855)
#2 0x0000564f0931ceb0 OsAbort (Xwayland + 0x1aceb0)
#3 0x0000564f09321dd9 AbortServer (Xwayland + 0x1b1dd9)
#4 0x0000564f09322b2a FatalError (Xwayland + 0x1b2b2a)
#5 0x0000564f091b9ce3 InitOutput (Xwayland + 0x49ce3)
#6 0x0000564f092e7744 dix_main (Xwayland + 0x177744)
#7 0x00007f4a3a7ed062 __libc_start_main (libc.so.6 + 0x24062)
#8 0x0000564f091b733e _start (Xwayland + 0x4733e)
Feb 17 22:18:07 slimbook systemd[1]: systemd-coredump@0-1102-0.service: Succeeded.
Feb 17 22:18:07 slimbook systemd[760]: org.gnome.Shell@wayland.service: Failed with result 'protocol'.
Feb 17 22:18:07 slimbook systemd[760]: Failed to start GNOME Shell on Wayland.
Feb 17 22:18:07 slimbook systemd[760]: org.gnome.Shell@wayland.service: Triggering OnFailure= dependencies.
Feb 17 22:18:07 slimbook systemd[760]: Stopped target GNOME Wayland Session.
Feb 17 22:18:07 slimbook systemd[760]: Stopped target GNOME Session Manager is ready.
Feb 17 22:18:07 slimbook systemd[760]: Stopped target GNOME Shell.
Thankfully, I had a known good reference tree from a day ago so I started tracking modules till the issue was narrowed down to glib. After bisecting, it seems that the first problematic commit is the following glib@67a589e5
Good Night