GBM EGL display creation fails on Wayland + NVIDIA — workaround: WEBKIT_DISABLE_DMABUF_RENDERER=1

[estevaom]

Environment

• OS: Arch Linux (kernel 6.18.3)
• Display server: Wayland (Hyprland)
• GPU: NVIDIA RTX 4090
• App version: 0.7.45 (amd64 AppImage)

Problem

Launching the AppImage crashes immediately:

$ ./Codex.Monitor_0.7.45_amd64.AppImage
Could not create GBM EGL display: EGL_SUCCESS. Aborting...
Aborted (core dumped)

Workaround

Setting WEBKIT_DISABLE_DMABUF_RENDERER=1 resolves the issue:

$ WEBKIT_DISABLE_DMABUF_RENDERER=1 ./Codex.Monitor_0.7.45_amd64.AppImage

This is a known issue with WebKit's DMA-BUF renderer on NVIDIA + Wayland. The GBM EGL backend fails to initialize with NVIDIA's GBM implementation.

Suggestion

Consider adding this env var as a fallback when GBM EGL display creation fails, or document it for Linux/Wayland/NVIDIA users.

[Dimillian]

@codex any idea?

[chatgpt-codex-connector]

Summary

• Added a Wayland + NVIDIA detection guard to set WEBKIT_DISABLE_DMABUF_RENDERER=1 automatically when the NVIDIA kernel module is present, providing a built-in fallback for the GBM/EGL failure described in the PR. src-tauri/src/lib.rsL71-L93

Testing

• ✅ npm run lint
• ✅ npm run typecheck
• ⚠️ cargo check (failed: missing glib-2.0 development package / glib-2.0.pc not found in environment)

View task →