Desktop is freezing and I cannot pinpoint the issue

Desktop Environments Gnome
1

Hello there,

I’ve been using Endeavour OS (with GNOME) for a good ~3 months now.
While it works without any noticeable issues or hiccups on my old XPS 13, it runs into seemingly random freezes on my desktop PC.

One forced restart following a freeze ultimately killed my first install.

At this point I was convinced it was an issue caused by one of the GNOME Extensions. Now, only using two, it doesn’t seem to be that (anymore?). Instead I was sure it was LibreWolf, so I switched to Firefox only to have freezes using it as well.

Now on Vivaldi I had my first freeze yesterday.

Interestingly enough, I never had any issues playing resource hungry games - only on the desktop / when a browser was open and in use.

Now, I’ve got a couple of logs that hopefully can help identify the issue?
I’m a bit lost right now.

From last week (using mozilla):

[Fr Aug 22 00:30:29 2025] hub 10-0:1.0: config failed, hub doesn’t have any ports! (err -19)
[Fr Aug 22 00:30:29 2025] simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
[Fr Aug 22 00:30:29 2025] RAS: Correctable Errors collector initialized.
[Fr Aug 22 00:30:35 2025] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[Fr Aug 22 00:30:35 2025] cfg80211: failed to load regulatory.db
[Fr Aug 22 00:30:38 2025] xhci_hcd 0000:10:00.0: xHC error in resume, USBSTS 0x401, Reinit
[Fr Aug 22 00:30:48 2025] Bluetooth: hci0: Failed to send wmt func ctrl (-110)

From 4 days ago:

Aug 22 00:28:24 rocksteady librewolf.desktop[8192]: Crash Annotation GraphicsCriticalError: |[0][GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt (t=3461.57) [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt

From yesterday:

amdgpu 0000:03:00.0: [drm] ERROR [PLANE:88:plane-8] commit wait timed out
amdgpu 0000:03:00.0: [drm] ERROR flip_done timed out
amdgpu 0000:03:00.0: [drm] ERROR [CTRC:91:ctrc-0] commit wait timed out
amdgpu 0000:03:00.0: [drm] ERROR flip_done timed out
amdgpu 0000:03:00.0: [drm] ERROR [CTRC:91:ctrc-0] flip_done timed out

Apologies for the different formats. I started using gnome logs as a GUI, hoping to see through the logs a bit easier.

System information:

  • OS: EndeavourOS Linux x86_64
  • Kernel: 6.12.43-1-lts
  • Packages: 1070 (pacman), 7 (flatpak)
  • Shell: zsh 5.9
  • DE: GNOME 48.4
  • WM: Mutter
  • Terminal: gnome-terminal
  • CPU: AMD Ryzen 7 7700X (16) @ 5.573G
  • GPU: AMD ATI 15:00.0 Raphael
  • GPU: AMD ATI Radeon RX 6950 XT
  • Memory: 3197MiB / 31239MiB

Thank you so much for having a look at it.
I’d be very happy to be using it without the fear of a freeze coming along.

It’s much appreciated :folded_hands:

2

I wonder if this has anything to do with the relatively recent core updates. I, too, am facing the same issue, RIGHT AFTER these updates, with two of my old laptops. Both running Intel core duos & Mesa Intel graphics. No other of my machines, whether desktop or laptop was affected, no matter if they are older, newer or new.

I guess some new update will fix it, at some point.

Use the REISUB key combination (I think not installed by default) to avoid hard shutdowns. Here’s how…:

PS: I have found that disabling all widgets ( I am on KDE) & third party goodies from my desktop has helped the situation. After all, the system itself kills them in the cases when it didn’t just froze. :wink:

1 Like
3

I hope it really is something that will be fixed later on.
And hopefully I’ll notice, because I’d really like to continue using Gnome Extensions.
Some of them are just too useful.

Thanks for the tip using REISUB. This is my first time hearing about it.
I’ll see to implement that into my system​:folded_hands:

1 Like
4

UPDATE

How stupid of me. I had completely forgotten the existence of X11. So, instead of continuously restarting after losing DE elements & freezes, I remembered it, switched from Wayland to X11 &…voila! A trouble-free system again, as sound as ever. First time Wayland gave me an issue after many-many-many years, but there’s a 1st time for everything…

If you’re in the same situation, give it a try & let us know.

1 Like
5

EDIT
Switching to “GNOME on Xorg” in the Log In Screen is what you mean, yeah?
I’ll see if that does the trick. Thanks for bringing it up!

1 Like
6

Yes. Though I’m on different old hardware & KDE. Hope it will work for you, too.

1 Like
7

So, working with Xorg I don’t seem to get the full freezes anymore, but I get a different type where I can still use my cursor and it mouse-over still changes, but I cannot click anything anymore.

I’m not sure what’s causing it at all. Because no matter on Xorg or Wayland I’m consistently getting the following warnings:

  • Warning: Could not resolve keysym XF86DoNotDisturb
  • (WW) Warning, couldn’t open module vesa
  • WARNING: Desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop for application orca-autostart.desktop could not be parsed or references a missing TryExec binary
  • WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1

And a critical using Xorg yesterday evening

  • (process:46096): GLib-GObject-CRITICAL **: 00:49:32.051: g_object_unref: assertion ‘G_IS_OBJECT (object)’ failed

Despite that, how high are the chances that the random freezes using Wayland will be sorted out and how do I know that someone took note of the errors, could identify the cause and resolve them? Is there any time frame in which I can hope to see this alleviated?

8

Sorry to hear that. I’m sure that it’ll be sorted out at some point, so I can switch back to Wayland myself. I can’t be of any help, let’s hope someone will come up with some kind of solution or workaround.