@alex_h - I had another desktop incident today that might help with your troubleshooting. This comes after a fresh install, update and no carried over configs, doing everything from scratch. I didn’t install off lists etc. Just one program at a time. Had a day or two of stability. The only notable change in my daily workflow is switching to Firedragon from Brave as my daily driver.
This time it appears to be different from the Panel Colorizer crashes we’ve been tracking. Firedragon browser segfaulted hard across multiple processes, which killed the X server and closed all windows, triggering Plasma service restarts.
Browser crash sequence:
Sep 09 12:35:53 Sable kernel: Isolated Web Co[206304]: segfault at 0 ip 00007f11d0a4cad9 sp 00007ffcf244e040 error 6 in libxul.so
Sep 09 12:35:53 Sable kernel: Web Content[215646]: segfault at 0 ip 00007f11d0a4cad9 sp 00007ffcf244e040 error 6 in libxul.so
[...multiple similar crashes...]
Sep 09 12:35:53 Sable xdg-desktop-portal-kde[315082]: XIO: fatal IO error 4 (Interrupted system call) on X server ":1"
Sep 09 12:35:53 Sable systemd-coredump[315149]: Process 15346 (electron) of user 1000 terminated abnormally with signal 5/TRAP, processing...
Plasma services auto-restart:
Sep 09 12:35:53 Sable systemd[3610]: plasma-plasmashell.service: Scheduled restart job, restart counter is at 1.
Sep 09 12:35:53 Sable systemd[3610]: plasma-xembedsniproxy.service: Scheduled restart job, restart counter is at 1.
However, the Panel Colorizer corruption persisted after the restart - still throwing the same binding loops and null property errors we’ve been tracking, so I appear to have multiple stability issues affecting the system.
Full diagnostic output from today’s crash:
Broader crashes: https://0x0.st/Kq7O.txt
Display server issues: https://0x0.st/Kq7V.txt
Service restarts: https://0x0.st/Kq7W.txt
Panel Colorizer errors after restart: https://0x0.st/Kq71.txt
This suggests there might be multiple stability issues affecting Dr460nized setups beyond just the Panel Colorizer widget corruption. Your “desktop restarts like logout/login” symptom could have different root causes.
Can you run these diagnostic commands next time it happens to see what’s actually triggering your restarts?
# Check for broader system crashes that might be the real trigger
journalctl -b --since "30 minutes ago" | grep -E "crash|segfault|core dumped|fatal|killed|terminated|restart" | tail -30 | curl -F'file=@-' https://0x0.st
# Look for display server failures
journalctl -b --since "30 minutes ago" | grep -E "kwin|compositor|wayland|XIO|fatal IO error" | tail -20 | curl -F'file=@-' https://0x0.st
# Check for cascading service restarts
journalctl -b --since "30 minutes ago" | grep -E "systemd.*restart|Scheduled restart" | curl -F'file=@-' https://0x0.st
It seems likely worth distinguishing between widget crashes versus broader system instability. The Panel Colorizer appears to be broken, but there might be other failure modes at play.
