Youwee LogoYouwee

Debugging

Troubleshoot startup, rendering, and environment-specific issues, especially on Linux systems using WebKitGTK and Wayland.

Blank or white window on Ubuntu 24.04 / 26.04

If Youwee launches but only shows a blank or white window, and the terminal prints repeated EGL, DMABuf, or framebuffer-related messages such as Failed to create EGL image from DMABuf, you are most likely hitting a Linux WebKitGTK rendering issue rather than an app-specific download failure.

This tends to appear on Wayland sessions, newer Ubuntu releases, and some Mesa or NVIDIA driver combinations. The common pattern is that libwebkit2gtk-4.1 chooses a rendering path that does not cooperate with the system graphics stack.

Quick fix from a terminal

Start Youwee with both fallback flags enabled:

WEBKIT_DISABLE_DMABUF_RENDERER=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 youwee

If you are launching the AppImage directly, use:

WEBKIT_DISABLE_DMABUF_RENDERER=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 ./Youwee_*.AppImage
What these flags do: WEBKIT_DISABLE_DMABUF_RENDERER=1 disables the DMA-BUF renderer path, and WEBKIT_DISABLE_COMPOSITING_MODE=1 disables a compositing path that can still leave the webview blank on affected systems.

Confirm the environment

Check whether your desktop session is running on Wayland:

echo $XDG_SESSION_TYPE
  • If the result is wayland, this issue is more likely.
  • If running from a terminal shows repeated AcceleratedSurfaceDMABuf, EGL, or Wayland protocol errors, the rendering stack is the first thing to debug.
  • If the app fails before any UI appears, also verify that libwebkit2gtk-4.1-0 is installed.
sudo apt update && sudo apt install libwebkit2gtk-4.1-0

Arch Linux: could not create GBM EGL display: EGL_SUCCESS

GitHub discussion #69 reports a separate Linux graphics failure on Arch-based systems:

could not create GBM EGL display: EGL_SUCCESS. Aborting...

This points to a GBM/EGL initialization problem in the WebKitGTK rendering stack. For this specific case, the recommended workaround is to disable the GBM path instead of using only the generic DMA-BUF and compositing flags.

WEBKIT_DMABUF_RENDERER_DISABLE_GBM=1 youwee

If you are running the AppImage directly:

WEBKIT_DMABUF_RENDERER_DISABLE_GBM=1 ./Youwee.AppImage
Persistent setup: add WEBKIT_DMABUF_RENDERER_DISABLE_GBM=1 to your shell profile or prepend it in the desktop launcher:
Exec=env WEBKIT_DMABUF_RENDERER_DISABLE_GBM=1 youwee

Make the fix permanent

If the terminal workaround fixes the UI, update the app launcher so Youwee always starts with the same environment variables.

  1. Locate the .desktop file, usually in ~/.local/share/applications or /usr/share/applications.
  2. Edit the Exec= line to prepend the variables before the launch command.
Exec=env WEBKIT_DISABLE_DMABUF_RENDERER=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 youwee

For AppImage launchers, keep the same prefix and point the command to the full AppImage path instead of youwee.

Related docs

InstallationDependencies