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

Wine and Proton stay on XWayland even though the Wayland driver exists

omarchyarchendeavouroscachyosmanjarohyprlanddesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The plain Wine half of this record is correct and I confirmed it against Wine source rather than only against the wiki, which matters because the wiki cites the wine-10.0 release notes and this workstation runs wine 11.16-1. In wine 11.16 programs/explorer/desktop.c line 43 sets default_driver = L"mac,x11,wayland", and the loader walks that comma-separated list building wine%s.drv and taking the first LoadLibraryW that succeeds, so X11 genuinely does win when both work. The same function reads HKEY_CURRENT_USER\Software\Wine\Drivers value Graphics at lines 1011 to 1015, so the record's registry path and value name are exact. DISPLAY=:0 is set in this Omarchy session (checked with systemctl --user show-environment), so the X11 driver loads and the record's cause holds here. winewayland.drv is present in /usr/lib/wine/x86_64-windows/. The nodrv_CreateWindow and The explorer process failed to start. strings are in dlls/win32u/driver.c lines 772 to 981, and Could not create tray window is in the Arch wiki block the record quotes. The verify line is exact: hyprctl clients on this machine prints xwayland: 0 per window. One claim is wrong and it is the Proton half. PROTON_ENABLE_WAYLAND does not exist anywhere in Valve's own Proton. I fetched the proton launcher from proton_10.0, proton_11.0, experimental_11.0 and bleeding-edge and enumerated every PROTON_* variable in each: none of them is a Wayland variable, and GitHub code search across ValveSoftware/Proton and ValveSoftware/wine returns zero hits for the name. It is a GE-Proton option, introduced in the GE-Proton10-1 release notes on 2025-05-14 (New option for using Wine-Wayland: PROTON_ENABLE_WAYLAND=1), and it is also read by proton-cachyos, whose launcher calls check_environment("PROTON_ENABLE_WAYLAND", "wayland"). So the record's own hedge, Proton 10 / Proton Experimental or a recent Proton-GE, is wrong in two of its three arms: a stock Proton 10 or Proton Experimental silently ignores the variable, which is the exact failure shape of a setting nothing reads. The GE release notes also tell users not to unset DISPLAY when using it, which the record does not mention. The Hyprland XWayland source resolves but is about HiDPI scaling and abstract Unix sockets and says nothing about Wine, Proton, mouse offset or flicker, so it does not support what the record claims and is removed. NOT exercised: I ran no wine, no winecfg, no game and no Steam client, and wrote no registry value, because this is the operator's daily workstation.

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

PROTON_ENABLE_WAYLAND=1 is a GE-Proton option and is experimental. It breaks the Steam overlay in most games (reported against Baldur's Gate 3, Diablo 3, Overwatch 2 and Path of Exile 2 among others) and MangoHud may fail to draw or crash the game. Set it per game in Launch Options rather than globally, so you can drop it for any title that misbehaves. Setting Graphics to a bare wayland in the prefix registry leaves no X11 fallback, so if winewayland.drv fails to load the prefix has no graphics driver and applications exit with nodrv_CreateWindow.

Symptom

Games under Proton have laggy or offset mouse input, flicker, or refuse to go properly fullscreen. I read that Wine has a native Wayland driver now, but wine still behaves exactly like before and setting an environment variable did nothing. winecfg windows sometimes open with no keyboard or mouse response at all.

Cause

Wine's Wayland graphics driver is built and shipped, but the X11 driver still takes precedence whenever both can load. Wine 11.16 sets default_driver = L"mac,x11,wayland" in programs/explorer/desktop.c and tries each name in order, and under a Wayland session DISPLAY is always set because XWayland is running, so winex11.drv loads first and wins.

Valve's own Proton is a separate matter. Proton 10, Proton 11, Proton Experimental and bleeding-edge have no Wayland environment variable at all. PROTON_ENABLE_WAYLAND=1 is a GE-Proton option added in GE-Proton10-1, also honoured by proton-cachyos and set by launchers such as Lutris and Heroic. Setting it in Steam launch options under a stock Valve Proton does nothing.

Fix

**Plain Wine, one-off:** unset DISPLAY for that invocation.


env -u DISPLAY wine example.exe

**Plain Wine, prefix-wide:** write the driver preference into the prefix registry. The value is a comma-separated list tried in order, so wayland,x11 keeps an X11 fallback if winewayland.drv fails to load, while a bare wayland leaves you with no graphics driver if it does.


wine reg add 'HKEY_CURRENT_USER\Software\Wine\Drivers' /v Graphics /d 'wayland,x11'

Revert with:


wine reg delete 'HKEY_CURRENT_USER\Software\Wine\Drivers' /v Graphics /f

**Proton / Steam:** PROTON_ENABLE_WAYLAND=1 is a **GE-Proton** option, not a Valve one. Stock Proton 10, Proton 11 and Proton Experimental have no Wayland variable and ignore it silently, so check which Proton the game is using first. Install GE-Proton, select it for the game under Properties then Compatibility, and set the variable in Launch Options:


PROTON_ENABLE_WAYLAND=1 %command%

GE's own release notes say that is all you need, and that you should not additionally blank DISPLAY, because unsetting it breaks applications that still want X11.

**If XWayland behaviour is what you actually want to fix** (flicker, wrong window location, wrong mouse position, keyboard not detected), the documented Wine workaround is a virtual desktop. In winecfg, Graphics tab, tick "Emulate a virtual desktop". If the window is already unresponsive and you cannot reach that checkbox:


wine explorer /desktop=name,1280x800 winecfg

If GUI windows never appear and you see nodrv_CreateWindow ... no driver could be loaded / Could not create tray window, try forcing a display:


DISPLAY=:1 wine winecfg

On Omarchy nothing here is overridden by the session. /usr/share/omarchy/default/hypr/envs.lua sets GDK, Qt, Electron and Mozilla variables only, and no Wine or Proton ones. Do not move the DISPLAY change into ~/.config/uwsm/env.d/: that is the session-wide override point and unsetting DISPLAY there would break every XWayland application, not just Wine.

Verify

With the Wayland driver active, hyprctl clients shows the Wine/Proton window with xwayland: 0. Mouse position tracks correctly in fullscreen and the window no longer flickers between sizes.

Sources

wine-proton-native-wayland-driver