fix(desktop): disable WebKit DMABUF renderer by default on Linux#646
Merged
nadaverell merged 1 commit intomainfrom May 6, 2026
Merged
fix(desktop): disable WebKit DMABUF renderer by default on Linux#646nadaverell merged 1 commit intomainfrom
nadaverell merged 1 commit intomainfrom
Conversation
WebKitGTK's DMABUF renderer (default since 2.42) produces blank/black windows on a range of Wayland setups — KDE KWin, NVIDIA, some Mesa stacks. Upstream closed the regression as an application-level concern, so the Tauri/Wails/WebKit2GTK app ecosystem has converged on shipping the WEBKIT_DISABLE_DMABUF_RENDERER=1 workaround by default. The legacy renderer is stable everywhere. Set the env var only when unset (LookupEnv, not empty-string), so users who explicitly set WEBKIT_DISABLE_DMABUF_RENDERER=0 can opt back in. Must run before Wails initializes WebKit, so it's wired in early in main() right after logBootEnv(). Linux-only via build tags; no-op stub on other platforms. Closes #465.
|
You have used all Bugbot PR reviews included in your free trial for your GitHub account on this workspace. To continue using Bugbot reviews, enable Bugbot for your team in the Cursor dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
WebKitGTK's DMABUF renderer (the default since 2.42) produces blank/black windows on a number of Wayland setups — KDE KWin, NVIDIA, some Mesa stacks. The user in #465 hit this on Fedora 43 KDE; the standard
WEBKIT_DISABLE_DMABUF_RENDERER=1workaround fixed it.Upstream WebKit considers this an application-level concern (won't fix in WebKitGTK), and the Tauri / Wails / WebKit2GTK app ecosystem has converged on shipping the workaround by default. The legacy renderer is stable everywhere — no known regressions from disabling DMABUF.
What changed
applyWebKitDefaults()setsWEBKIT_DISABLE_DMABUF_RENDERER=1at startup, only when the variable is unset. Users can opt back in withWEBKIT_DISABLE_DMABUF_RENDERER=0.LookupEnv(not empty-string check) so an explicit=0is respected.main()right afterlogBootEnv(), before Wails initializes WebKit.If users still see blank windows after this ships, the next escape hatch is
WEBKIT_DISABLE_COMPOSITING_MODE=1— kept as a manual fallback rather than another default, since it forces a much slower software-rendered path.Closes #465.