#16139
Issues/omacom/omarchy/#16139

cursor-bin on Wayland aborts with SIGTRAP after electron42/Mesa update; --disable-features=Vulkan fixes it

Openumangbpopened 20h ago

System details

Intel Raptor Lake-P Iris Xe [8086:a7a0] (Framework, i915), Omarch 4.0.6-1

What's wrong?

Summary

After updating Omarchy 4.0.4 → 4.0.6, Cursor (cursor-bin) became unstable on Intel + Wayland: renderer processes were SIGKILL'd, then the main process aborted with SIGTRAP. Omarchy forces Electron onto Wayland (ELECTRON_OZONE_PLATFORM_HINT=wayland in default/hypr/envs.lua) and runs Cursor on system electron42. Electron 42 then selects Vulkan (vulkan-intel). Chromium's Wayland ozone backend rejects that pair, the GPU process dies, and Electron aborts with SIGTRAP (GPU process isn't usable. Goodbye.). This is an Omarchy packaging/config bug, not a Hyprland crash. XWayland (--ozone-platform=x11) avoids the abort but looks blurry on fractional scale (1.5 / 1.175). Disabling Vulkan while staying on Wayland restores both stability and sharp fonts.

System

Omarchy4.0.6-1
Kernel7.2.8-9-omarchy
GPUIntel Raptor Lake-P Iris Xe [8086:a7a0] (Framework, i915)
CompositorHyprland 0.56.2-4
cursor-bin3.26.13-1 (was 3.24.12-1)
electron4242.11.14-2 (was 42.9.3-1)
mesa / vulkan-intel1:26.2.5-1 (was 1:26.2.2-1)
Update landed 2026-10-21 ~10:28 local. No OOM. No i915 GPU reset. Cores were not retained (COREFILE missing).

What happened

  1. Launch Cursor from the app launcher after the 4.0.6 update.
  2. UI runs for minutes (sometimes ~15s on a fresh launch), then:
    • CodeWindow: renderer process gone (reason: killed, code: 9)
    • systemd-coredump: Process … (cursor) … signal 5/TRAP
  3. Forcing XWayland stops the crash but fonts/UI look bad on HiDPI.
  4. Native Wayland + --disable-features=Vulkan is stable and sharp. Journal:

Oct 21 14:39:26 systemd-coredump: Process 554972 (cursor) of user 1000 terminated abnormally with signal 5/TRAP

GPU process after the working flags:

electron --type=gpu-process --ozone-platform=wayland --render-node-override=/dev/dri/renderD128 --disable-features=…,Vulkan

Cursor window is xwayland=false.

Expected

Cursor stays on Wayland (Omarchy's default), keeps GPU compositing via GL/EGL, and does not SIGTRAP.

Workaround (user)

~/.config/cursor-flags.conf:

--ozone-platform=wayland --disable-features=Vulkan

Do not recommend --ozone-platform=x11 as the default on fractional-scale setups.

Proposed Omarchy fix

Bake the Vulkan disable into the cursor-bin launcher (/usr/share/cursor/cursor), which already forwards electron42-flags.conf:

electronflags+=("--disable-features=Vulkan")

Better: ship a default electron42-flags.conf (via omarchy-settings) with --disable-features=Vulkan, because every Electron 42 app inherits ELECTRON_OZONE_PLATFORM_HINT=wayland. Chromium already logs the same line (wayland_surface_factory.cc: '--ozone-platform=wayland' is not compatible with Vulkan). Related: https://github.com/basecamp/omarchy/issues/5372

Upstream (not the first report)

Chromium/Electron documents the incompatibility. Other Electron 42 apps (Claude/Hermes desktop) ship --disable-features=Vulkan on the Wayland path. Omarchy can do the same without waiting on Electron.

Activity

0

No activity yet.