Skip to content

fix: WebKit DMA-BUF fallback on NVIDIA + Wayland (0.2.3) - #13

Merged
ildella merged 2 commits into
masterfrom
fix/nvidia-wayland
Oct 5, 2026
Merged

ildella merged 2 commits into
masterfrom
fix/nvidia-wayland

Conversation

@ildella

@ildella ildella commented Oct 5, 2026

Copy link
Copy Markdown
Owner

Discovered while testing the sayit-bin OPR package on Omarchy (Crasto, GTX 1060 + Hyprland/Wayland): sayit-desktop aborts with

Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display.

WebKitGTK's DMA-BUF renderer is broken on NVIDIA. The app now detects an NVIDIA GPU in main() (/dev/nvidia0 or /sys/module/nvidia) and sets WEBKIT_DISABLE_DMABUF_RENDERER=1 before the webview is created, unless the user already set the variable. Verified on the machine above: the packaged binary now starts with no env var.

README gains a short NVIDIA/Wayland note in the Wayland section.

Bump to 0.2.3 (package.json + Cargo.toml + Cargo.lock) so the OPR recipe re-renders on the fixed release.

Refs OSP-16.

WebKitGTK's DMA-BUF renderer aborts with 'Error 71 (Protocol error)
dispatching to Wayland display' on NVIDIA. Detect an NVIDIA GPU in main()
and set WEBKIT_DISABLE_DMABUF_RENDERER=1 before the webview is created, so
the shipped app starts out of the box on Omarchy/NVIDIA. Documented in the
Wayland section of the README.
@ildella
ildella merged commit 7dcc88b into master Oct 5, 2026
1 check passed
@ildella
ildella deleted the fix/nvidia-wayland branch October 5, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant