Fix blank screen / Crash on Linux due to Wayland, NVIDIA, etc
Bug
Possible error messages:
Error 71 (Protocol error) dispatching to Wayland displayCannot create EGL context: invalid display
If Yaak crashes or shows a blank screen on Linux, try setting one of the following environment variables:
WEBKIT_DISABLE_COMPOSITING_MODE=1forces accelerated compositing off in WebKitGTK.WEBKIT_DISABLE_DMABUF_RENDERER=1disables the newer DMA-BUF renderer, which is the default in recent WebKitGTK and is generally the right path—except it’s been flaky with NVIDIA proprietary drivers(white/blank screens, flicker).__NV_DISABLE_EXPLICIT_SYNC=1makes the driver / EGL-Wayland layer turn off or ignore the explicit sync path and fall back to older (less strict) synchronization paths
Linux
Closing this one. The NVIDIA plus Wayland crash is handled automatically since 2026.6.0, and the remaining AppImage cases are covered in Blank screen or crash on Linux. If you see it again on a current version, let me know here.
I was able to extract the AppImage and replace libraries in ./usr/lib/ with versions from my system /usr/lib to get it working.
There are now AUR packages, if you would like to try them:
https://aur.archlinux.org/packages/yaak-app
https://aur.archlinux.org/packages/yaak-app-beta
SoftExpert thanks, the deb based package is working great!
Tauri has a few bugs regarding Linux AppImage support at the moment. This one could be related to this? https://github.com/tauri-apps/tauri/issues/9304
( please note that i cant tesst the git version or the bin versions or whatever becouse web2kitgtk whatever version 4.2 doesnt want to download either becouse of issues with keys or becouse its not available on the mainrepo.
This is likely the issue you’re facing. There’s a workaround near the bottom
https://github.com/yaakapp/app/issues/80#issuecomment-2345260666
There are also a couple AUR packages for Yaak, which work https://aur.archlinux.org/packages/yaak
version 2024.12.0 appimage not work in manjaro
but the appimage I build by myself works…
I have the same issue on Arch with hyprland.
Same issue here, using both the stable & beta versions of the app using Fedora 42.
Is this using the RPM package to install?
I tried the RPM package. It has the same issue when launched from the app menu, but it works fine when run from the terminal.
I suspect it’s failing to read some environment variables.
related:
- https://feedback.yaak.app/p/yaak-shows-gray-screen-after-opening-appimage
https://feedback.yaak.app/p/app-not-starting-with-blank-ui-on-popos-2204-lts
This issue was solved in the recent release (2025.5.0).
Thanks for Yaak. 🧁
Sounds like your missing some video drivers. EGL is “OpenGL ES / Vulkan”. I’d start by installing the mesa drivers. It could also be an issue between X11 and Wayland.
Related. 2025-08-19, Fedora 42, Yaak 2025.5.6 (AppImage).
I’m marking this as “Won’t Fix” because there isn’t really anything I can do in the app. I’ve update the main description with a workaround.
Running Arch Linux. The only way I got Yaak to run properly on Gnome 49 (Wayland) is by installing yaak-bin from AUR.
Same on Arch with X11. Launching it as:
WEBKIT_DISABLE_DMABUF_RENDERER=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 ./Desktop/yaak.AppImageGetting blank gray screen. Is this the better than postman experience?
On Arch (Intel hardware), I got this error:
Could not create default EGL display: EGL_BAD_PARAMETER. Aborting...I could fix it by running:
LD_PRELOAD=/usr/lib/libwayland-client.so yaakNot sure if the underlying problem is the same, but my experience (on Ubuntu 25.10 + NVidia + AppImage + Wayland) is that the UI launches fine but eventually stops updating/re-rendering (usually after focusing another application and then returning).
In this state the app is effectively frozen, though the mouse cursor still changes as I hover over places where text inputs and resize handles should be (and I can still exit using Alt+F4 without losing my changes).
Same problem here, AppImage doesn’t work. Best solution is Flatpak, please add support.
Setting
WEBKIT_DISABLE_COMPOSITING_MODE=1at theExec=line in Yaak’s desktop entry file fixed this issue for me on Wayland:Of course you’ll need to complete some base steps like you would with any other Electron / Tauri app Wayland fixes, like copying the desktop entry first from
/usr/share/applications/and reloading the desktop entries.Ubuntu Solution to blank screen
I made a script for Ubuntu users that installs Yaak the right way. Might work for other distros.
Steps
What the script does?
It creates an app shortcut with the appropriate ENV so the app runs on your machine. You can always change the env for one of the other ones if you are on Wayland.
Script
The url to this story on dev.to: https://dev.to/greggcbs/yaak-blank-screen-quick-fix-ubuntu-1o84
Guys, this is the top 1 problem that appears in this forum, users cannot use it on Linux, please fix it, Appimage is not viable anymore (most distros don’t ship fuse2 anymore, it’s deprecated), community is moving towards Flatpak.
I’m having this issue as well. On Manjaro (6.6.128-1-MANJARO) using Hyprland + Wayland.
It crashes on
Gdk-Message: 10:08:59.101: Error 71 (Protocol error) dispatching to Wayland display.Full Log:
I had problem with blank screens in appimage before Yaak with other Tauri software in Arch with Hyprland, and now I’m having the same problem, but don’t have this problem with the AUR package. Probably something related to fuse2? Maybe flatpak is a better option?
Documented the known fixes here: Blank screen or crash on Linux
I’ve had Yaak trigger a crash notification after I intentionally closed it. It seems related to NVIDIA/WebKit, but unlike most reports here, the app opens and works - the crash happens on exit.
I’m using:
I checked the system logs with an assistant. There are three recorded crashes, on September 30, October 6, and October 12. All three are Yaak’s WebKitWebProcess, crashing with SIGSEGV in the SkiaGPUWorker thread inside libnvidia-eglcore.so.610.57.04.
For the latest one, Yaak logged application-exit cleanup at 12:52:16 CEST, and the renderer crashed a second later. The main thread was already in exit() and NVIDIA EGL cleanup. Part of the crashing thread’s stack is:
I tried twice more afterward: once opening Yaak, running a request, interacting with the title bar, and closing it; then once just opening and closing it. Neither produced another core dump, so it seems intermittent.
I saw the comment saying the NVIDIA/Wayland crash is handled since 2026.6.0. I’m on a later version, but I don’t know if this is the same problem or a separate shutdown issue. I haven’t tried the latest release or the environment-variable workarounds yet.
Is this worth tracking here, or should I make a separate report? I can provide more redacted logs if needed.
This is a different crash from the one this post covered. That one happened at startup. Yours is WebKit’s renderer process segfaulting in the NVIDIA EGL driver during shutdown, after Yaak has already exited. Since the crash is inside WebKitGTK and the driver, Yaak’s code has little control over it, and updating to 2026.9.0 won’t change it. The most likely fix is launching with
WEBKIT_DISABLE_DMABUF_RENDERER=1, which takes WebKit off the GPU path that’s crashing. Please open a separate post after a week or so, saying whether the crash notifications stopped.