Question: Gnome session just reboots/closes

Bluefin
1

Hi,

Before reporting this as an issue, I’d like to debug it further to understand if it is my laptop, bluefin or something I did.

It has been already a couple of times during the last month that my Gnome Session just closes/reboots. Out of the blue, I get the login screen as if I had rebooted the system. All applications are closed, of course, and data not saved is lost.

Did anyone else experienced this on Bluefin?

How/Where could I find more information about what happened? I did not find too much with journalctl -xe

PD: I use bluefin on a Framework 13 AMD

2

This sounds like your GNOME session crashing. Something I would investigate first is GNOME extensions, if you’ve added some I’d see if one of them is causing this (usually shutting them off can help find the one).

The ones we ship stock are from the fedora repos and are generally stable (we have enough people using AMD Frameworks that I don’t suspect it’s an extension we ship), a few times a month sounds way too high though.

3

Thanks for the tip.

I have three extensions installed but only one enabled: Random Wallpaper. I’ll follow your advice and disable it to see if that is the cause.

4

Hey @mmartinortiz
I have had the same issue happen a couple of times as well.
After I login again I noticed that the gnome extensions were disabled.
But I haven’t gone through the trouble of finding out which one is causing the crash.

1 Like
5

ah, finally someone else
this has been very annoying, though I get it’s most likely not Bluefin’s fault?
usually when I log in after a restart, GNOME crashes? and I am prompted to log in again, and when I do, I see that Extension Manager is disabled
I re-enable it, and then the same thing happens at some point later
I haven’t installed any extra extensions besides what already comes with BF
one thing I believe I had success with, is when the machine restarted and I logged in, to wait 1 minute and do nothing, I’ve never had it crashed if I do that, kind of like giving it time to kick off all the processes properly?

1 Like
6

might be a good idea to check the pre-installed extensions…
I am a heavy launcher user, and I probably summon the search light extension the second the machine logs in, maybe that’s the culprit, I should test it…

7

Ok, I just tested that and pretty sure that’s it.
Here’s what happened:

  • I restarted the machine, logged in, called search light right away and started running commands

  • Boom, GNOME crashed, I had to log in again

  • I check the logs and this is what it shows:
    image

  • I disable search light extension

  • I restart and log in

  • I start doing things right away - all good, GNOMEs not crashing

  • The logs don’t show that entry

  • For good measure I re-enable search light and restart the machine again

  • I log in and start doing things in search light right away

  • GNOME crashes, I have to log in again

  • The logs show that same stacktrace from the previous time it happened

This is an AMD machine if that matters.

1 Like
8

Great to here!
Sounds like you should open an issue on the search light GitHub repo.
I see that other people experience the same / similar issues.