Edit:
Well this turned out weird...
My post was moved to its own thread.
Anyway, for anyone that's interested I get a WSOD (white screen of death) when logging in tom my Zorin 18 OS after it has been sleeping (or something). I don't get the WSOD at login if I just lock my desktop and then a few minutes later log in again.
I would like to see this fixed in general, I rather not type some stuff in the terminal. Even though I know how to use the terminal I think it beats the purpose of Zorin OS, it should be for normal users - i.e not programmers.
Anyway... The WSOD is extremely frustrating since it force-shuts down all applications and who knows what happened to active work. This would send any normal person back to Windows 11 in a heart beat.
At least give me a log to look at or an error code. Now there's no info at all when it crashes.
---- Original post:
Just a ping here to keep track of this bug. I have the exact same issue with the WSOD. - And I'm not! going to do any terminal stuff to get it fixed!
My system info:
Systemdetaljrapport
Rapportdetaljer
Genererad: 2026-01-31 09:36:30
HĂĄrdvaruinformation:
HĂĄrdvarumodell: ASUS ROG STRIX B550-I GAMING
Minne: 32,0 GiB
Processor: AMD Ryzen™ 5 5600G with Radeon™ Graphics × 12
In your BIOS Settings, is Secure Boot Enabled or Disabled?
How often do you experience the Gnome Shell Crash?
Do you notice any correlation between running certain programs and when it crashes?
Have you been monitoring hardware temperatures?
Have you checked if Root Space is filled or near filled in "Disks" application or "Disk analyzer"?
I moved your post to its own thread in order to keep solutions separate. If you post in another persons thread and one of you finds a solution that works, but the other does not - then we would need to separate them, anyway.
I have plenty of disk space free, about 1TB. But I need to look into the secure boot thing, I think it's active since it usually is on by default I think. I look into it.
The Gnome crash usually happens when the computer have been sleeping, like in the morning. So it depends.
i haven't noticed that any particular applications are related to the WSOD but I mostly game on my computer, Steam games that is.
What I have noticed though is that the Zorin Apperance settings are always reset to the default settings and I have to re-do my setup when I log in after the crash. I don't know the name of the layout, but I use the top left layout in Zorin Appearance.
Just a question... I know I said I wouldn't type any s--it in the terminal but here I am and I wan't stuff fixed - so are there any good commands to type to see relevant error logs?
Yes, journalctl is your friend in this.
Your reticence to turn to the terminal makes sense if unguided and alone. You are not alone.
You do not need to be as programmer, but you can use the minds on this forum to help you disseminate the terminal and ease your life a bit.
journalctl -b -p err..alert
That should narrow entries down to a short list.
Since you are seeing a Gnome Shell crash, you might try:
journalctl -b | grep gnome-shell
These are a good starting point - you can then relay the output here in this thread in a team effort.
But for me, it is after 3am here and I need to fall into a coma.
Ah... I've read that Zorin Appindicator have some issues and it seems like that might be the case here as well. I just don't understand why it should cause a WSOD.
I ran "journalctl -b | grep gnome-shell" and got this:
The session has no shell to fall back to when software is integrated into the shell as Gnome does.
GNOME attempts a restart, then the same extension crashes again, GDM aborts the session and shows the error screen.
