I recently updated (stable channel) and got the gnome 40.1 update. After a reboot, GDM started crashing on startup (“oh no! something has gone wrong…”)
I installed plasma and switched to SDDM. Logging in to plasma worked. Logging in to gnome shell from SDDM produced the exact same error, but in gnome shell rather than GDM.
After grepping through journalctl for a bit, all I could find was:
Nov 23 23:25:26 mel gnome-shell: Running GNOME Shell (using mutter 41.0) as a X11 wind ow and compositing manager Nov 23 23:25:26 mel gnome-shell: Enabling experimental feature 'scale-monitor-framebuf fer' Nov 23 23:25:26 mel gnome-shell: ATK Bridge is disabled but a11y has already been enab led. Nov 23 23:25:26 mel gnome-shell: Settings schema 'org.gnome.desktop.lockdown' does not contain a key named 'disable-show-password' Nov 23 23:25:26 mel audit: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 pid=7376 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=5 res=1 Nov 23 23:25:26 mel gnome-shell: == Stack trace for context 0x561539e2b180 == Nov 23 23:25:27 mel systemd-coredump: Process 7376 (gnome-shell) of user 1000 dumped core. Found module libgnome-shell-menu.so with build-id: 0c937542cc359153908f6098d414c7414ed85230 Found module libgnome-shell.so with build-id: ccc1f98479959b88dbd13ea6513582be82aca7ef Found module gnome-shell with build-id: 3dadc6c6e5cfce2437308618946a1bcf670b57f7 #1 0x0000561538975b09 n/a (gnome-shell + 0x2b09) #5 0x000056153897590c n/a (gnome-shell + 0x290c) #23 0x00007f7aac734f08 n/a (libgnome-shell.so + 0x35f08) #24 0x00007f7aac7201f5 n/a (libgnome-shell.so + 0x211f5) #27 0x000056153897545c n/a (gnome-shell + 0x245c) #29 0x000056153897572e n/a (gnome-shell + 0x272e)
gdm back to 40.1 fixed the issue.
Anything else I could look for in order to find out why gnome shell core dumped? grepping for mutter or clutter in the logs did not show anything useful.
I run a pretty vanilla install of manjaro, so I am wondering if this is something I should report upstream.