Title: Native + Electron apps spin at 100% CPU with no window after Sep updates (xserver 1.8?)

Chat about Zorin
1

Zorin OS 18.1 (noble base, GNOME), kernel 7.0.0-34-generic (also tested 7.0.0-31),
xserver-xorg-core 1.8, NVIDIA 595.91 (was 580), Intel UHD + RTX 3070 Mobile (Predator PH315-54).

After updates of Sep 25 (kernel 31→34) and Sep 28 (xserver 1.6→1.8 + firmware),
several apps stopped opening: spinning cursor / 100% single-core CPU, no window, no log:

  • Div Acer Manager Max GUI (native .NET 9 Avalonia, incl. 2025 v0.9.1 build)
  • Postman (Electron)
  • warp-taskbar (Cloudflare deb, systemd user service, respawns)
    Same on X11 and Wayland, both kernels, two NVIDIA drivers.
    flatpak/bubblewrap already fixed (.3 installed) — these are native packages.
    ldd clean, nvidia-smi healthy. Daemons work (DAMX daemon serves all features via socket).
    Looks system-wide, matches "apps stopped opening" threads. Any known xserver/Mesa regression?
2

new nvidia 595 + xserver 1.8 can do that on hybrid for me. apps just spin w/ no window

check:
-prime-select query
-try once: __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia postman
-and LIBGL_ALWAYS_SOFTWARE=1 on the avalonia / DAMX binary
-journalctl --user -b | rg -i 'nvidia|GLX|EGL|electron'

if software gl opens them, id roll nvidia back to 580 from additional drivers for now

3

Welcome to the Forum!

Maybe it is related to that:

4

Tested both on DAMX (native .NET Avalonia):

  • prime-select: on-demand
  • __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia → still hangs (124, no output)
  • LIBGL_ALWAYS_SOFTWARE=1 → still hangs (124, no output)
  • user journal: no GLX/EGL errors, only monitor probing
    So neither offload nor software GL opens it — rolling back to 580 likely won't help (it broke on 580).
5

Thanks, that fixed it! fc-cache -fv found invalid cache files in ~/.cache/fontconfig
(c57959a1... and d0972c3d...-le64.cache-9) and cleaned them. Right after, my Avalonia
GUI (DAMX, dead since the Sep updates) started for the first time: it connected to its
daemon (get_supported_features/get_all_settings in the log) and the window showed up.
Survived the app restart. Thank you!

1 Like
6

Please reboot to check if it then still works.