Gnome keeps crashing at random

Ask Fedora
, , ,
1

I recently upgraded a computer I had installed Fedora 39 in to Fedora 41.
Upgrade went smoothly, no errors, no packages to fix.
However I soon began experiencing crashes seemingly at random while playing games, screensharing or just generally using the computer, really.

I’ve tried swapping extensions and just disabling them all, but no luck, it seems.

I’m running Fedora 41 with an Nvidia GPU (3070 with proprietary drivers) on X11.
How can I figure out more about these crashes? Oh and to be clear when I say crashes I mean that “Oops, something went wrong” screen that has me log out.

2

There should be corresponding logs in the output from sudo journalctl that would be more informative than “Oops …”. (You’ll want to append something like --since=today or --since=-5min to limit the output to the more recent log entries.)

3

Thank you for your reply.

Funnily enough I haven’t had a single crash since I opened the thread.
I remembered that the crash would happen consistently when I waited a couple of minutes before login in through GDM. So I tried reproducing that scenario (after updating some packages), but I had a different error.

I let the computer wait at the GDM login screen, and it went into hibernation.
After I woke it up, the screen froze and would quickly (in a handful of seconds) hibernate again. It looped like that. After I tried to shutdown the system through the UI, the screen went completely dead save for a “_” prompt.

I then forced a shutdown through the power button and extracted a log all the way from an hour before. I trimmed this log immensely because of Discord and AppIndicator extension spamming it with what I understand to be completely unrelated information.
The AppIndicator error was responsible for the vast majority of the log file, so I had to trim it out, but here’s what it said:

Feb 21 20:26:32 fedora gnome-shell[2549]: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.Failed: error occurred in Get
                                          
                                          Stack trace:
                                            _promisify/proto[asyncFunc]/</<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:453:45
                                            @resource:///org/gnome/shell/ui/init.js:21:20
                                            ### Promise created here: ###
                                            getProperty@file:///usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/dbusProxy.js:89:33
                                            refreshProperty@file:///usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:306:48
                                            _refreshOwnProperties/<@file:///usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:192:32
                                            _refreshOwnProperties@file:///usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:190:51
                                            _onSignalAsync/refreshPropertiesPromises<@file:///usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:246:26
                                            _onSignalAsync@file:///usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:245:50
                                            async*_onSignal@file:///usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/appIndicator.js:204:14
                                            _init/<@file:///usr/share/gnome-shell/extensions/appindicatorsupport@rgcjonas.gmail.com/dbusProxy.js:40:43
                                            @resource:///org/gnome/shell/ui/init.js:21:20

So here’s the log file. I’m not so well versed in what is expected to be logged, so I don’t really know how to investigate further.

4

Funnily enough, not 10 minutes after I posted my previous reply, I was hit with another crash.
This time I took out a 5min log.

I haven’t trimmed this one at all, just in case anything in it is useful.

The crash seems to happen at this point:

Feb 21 22:02:49 fedora gnome-shell[2616]: **
Feb 21 22:02:49 fedora gnome-shell[2616]: Clutter:ERROR:../clutter/clutter/clutter-actor.c:5483:clutter_actor_finalize: assertion failed: (priv->grabs == NULL)
Feb 21 22:02:49 fedora gnome-shell[2616]: Bail out! Clutter:ERROR:../clutter/clutter/clutter-actor.c:5483:clutter_actor_finalize: assertion failed: (priv->grabs == NULL)
Feb 21 22:02:49 fedora audit[2616]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=3 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=2616 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=6 res=1
Feb 21 22:02:49 fedora gnome-shell[2616]: == Stack trace for context 0x55a1ed726280 ==
Feb 21 22:02:49 fedora gnome-shell[2616]: #0   55a1ed818768 i   resource:///org/gnome/shell/ui/init.js:21 (eda41a70c90 @ 48)
Feb 21 22:02:49 fedora systemd-coredump[30766]: Process 2616 (gnome-shell) of user 1000 terminated abnormally with signal 6/ABRT, processing...

However it’s not clear to me what caused it, and I couldn’t find much info looking up online.
I’ll try to see if another crash happens with all extensions disabled, just in case.

Here’s the log.

5

It looks like there is an open bug report against the appindicator extension:

6

Here is the bug report corresponding to your gnome-shell crash. I think this is the main one you need to keep an eye on:

Edit:

If I’m reading it right, the patch for this bug is expected to land for GNOME 48:

1 Like
7

Thank you very much!
Just knowing the fix will be available soon puts me at ease.

1 Like