Summary
OpenWork crashes immediately on startup on systems with an NVIDIA GPU under X11. The crash is caused by WebKitGTK's hardware compositing, which fails to create a GBM buffer. The Tauri app does not set WEBKIT_DISABLE_COMPOSITING_MODE=1 by default.
To Reproduce
- System with NVIDIA GPU + proprietary driver + X11 (not Wayland)
- Launch OpenWork
- Immediate crash with error:
Failed to create GBM buffer of size 2297x1368: Invalid argument
Expected behavior
OpenWork should either:
- Detect NVIDIA + X11 and disable compositing automatically
- Set
WEBKIT_DISABLE_COMPOSITING_MODE=1 as a safe default for Linux builds
- Gracefully fall back to software rendering instead of crashing
Actual behavior
The application crashes immediately with a GBM buffer allocation error. No fallback rendering is attempted.
OW version & Desktop info
- OpenWork: 0.11.194-1 (AUR)
- OS: Arch Linux x86_64
- GPU: NVIDIA (proprietary driver)
- Display server: X11 / KDE KWin
Additional context
Workaround:
export WEBKIT_DISABLE_COMPOSITING_MODE=1
openwork
This is a known issue with WebKitGTK + NVIDIA + X11 that affects many Tauri/WebKitGTK apps. Setting the env var has no negative side effects — it simply uses software compositing.
Summary
OpenWork crashes immediately on startup on systems with an NVIDIA GPU under X11. The crash is caused by WebKitGTK's hardware compositing, which fails to create a GBM buffer. The Tauri app does not set
WEBKIT_DISABLE_COMPOSITING_MODE=1by default.To Reproduce
Expected behavior
OpenWork should either:
WEBKIT_DISABLE_COMPOSITING_MODE=1as a safe default for Linux buildsActual behavior
The application crashes immediately with a GBM buffer allocation error. No fallback rendering is attempted.
OW version & Desktop info
Additional context
Workaround:
export WEBKIT_DISABLE_COMPOSITING_MODE=1 openworkThis is a known issue with WebKitGTK + NVIDIA + X11 that affects many Tauri/WebKitGTK apps. Setting the env var has no negative side effects — it simply uses software compositing.