OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
wayland-compat high occasional DISPUTE

Stop a global SDL_VIDEODRIVER=wayland preventing games from launching

omarchyarchendeavouroscachyosmanjarohyprlandwaylandxwayland
CORRECTED An auditor found the fix wrong or incomplete and rewrote it. · checked against Omarchy omarchy 4.0.4-1 on 2026-10-05
AUDIT NOTE

Omarchy 4 claim confirmed: /usr/share/omarchy/default/hypr/envs.lua on 4.0.4-1 has no SDL line. The hyprland-wiki environment-variables source still suggests hl.env("SDL_VIDEODRIVER", "wayland"). The Arch Wayland page says SDL3 and sdl2-compat pick Wayland by default when the compositor supports fifo-v1, and that SDL3's own name is SDL_VIDEO_DRIVER with SDL_VIDEODRIVER as a lower-precedence fallback. Issues #1047 and #2564 support the game list, the error strings and the env -u and SDL_VIDEODRIVER=x11 workarounds. The Omarchy 3 branch is wrong. Reading default/hypr/envs.conf at each tag: v3.1.4 to v3.3.0 set SDL_VIDEODRIVER,wayland, v3.4.0 and v3.6.0 set wayland,x11 (which commenters in both issues say still broke Proton games), and v3.7.0 has no SDL line (commit 1b2dfa1b "Remove SDL_VIDEODRIVER"). The record's Omarchy 3 advice to set env = SDL_VIDEODRIVER, contradicts its own Omarchy 4 advice and the #2564 reporter, who found an empty value did not work consistently. Rewrote that branch, widened the grep to SDL3's name and environment.d, and lowered frequency to occasional because no current Omarchy release sets the variable. Not exercised: no game launched.

The cause above was rewritten on 2026-10-05 to match this note; the fix was corrected by the audit itself.

Symptom

Some Steam games (Deadlock, The Finals, ARC Raiders, Squad, Crusader Kings 3, Horizon Chase Turbo) never open, or show Failed to initialize dependencies. A Lutris game prints Could not initialize SDL video subsystem (wayland not available). Trying SDL_VIDEODRIVER=xcb gives Couldn't initialize SDL: xcb not available.

Cause

SDL_VIDEODRIVER=wayland forces every SDL application onto the Wayland video driver. Games that bundle an older SDL without Wayland support, and Proton games that need SDL's windows driver, then fail to create a window. Current SDL3 and sdl2-compat already pick Wayland on their own when the compositor supports it, so the variable gains nothing. Omarchy 3 set it in default/hypr/envs.conf (wayland up to v3.3, wayland,x11 in v3.4 to v3.6, which still broke Proton games) and removed it in v3.7.0, which is why the reports are from Omarchy users. Omarchy 4 does not set it (/usr/share/omarchy/default/hypr/envs.lua on 4.0.4-1 has no SDL line), but the Hyprland wiki still lists it as a suggested variable, so it is easy to copy into your own config. xcb is a Qt name, not an SDL one. SDL's X11 driver is x11.

Fix

Find out whether it is set and where. SDL3 also reads SDL_VIDEO_DRIVER, so check both names:


printenv SDL_VIDEODRIVER SDL_VIDEO_DRIVER
grep -rn 'SDL_VIDEO_\?DRIVER' ~/.config/hypr ~/.config/uwsm ~/.config/environment.d /etc/environment 2>/dev/null

**Omarchy 4 / Hyprland 0.55+.** Delete the hl.env("SDL_VIDEODRIVER", "wayland") line you added, then log out and back in. Remove the line entirely rather than setting an empty value.

**Omarchy 3.** Releases before v3.7.0 set it in Omarchy's own defaults. Update with omarchy update, which brings a release without the line, and remove any env = SDL_VIDEODRIVER,... line from your own ~/.config/hypr/*.conf. Avoid env = SDL_VIDEODRIVER, with an empty value: the #2564 reporter found it did not reliably unset the variable.

**Per game, without touching the session.** Steam > game > Properties > Launch Options:


env -u SDL_VIDEODRIVER %command%

or force X11 for a native game:


SDL_VIDEODRIVER=x11 %command%

**All of Steam at once:**


env -u SDL_VIDEODRIVER steam

Verify

printenv SDL_VIDEODRIVER prints nothing in a new terminal after logging back in, and the game reaches its menu.

Sources

sdl-videodriver-wayland-env-breaks-games