Steam or Proton game crashes on launch

Games that vanish two or three seconds after you press Play, with no window and no error dialog, are one of the most common Steam complaints in the Omarchy tracker. The cause is almost never Hyprland itself. It is usually a 32-bit Vulkan driver that does not match your GPU, or an environment variable inherited from an older config.

Checked on v4.0.4 against the source snapshots for v3.8.4, v4.0.3 and v4.0.4.

The fix

1. Confirm what you are running, so you know which advice applies.

   omarchy version

2. Install the 32-bit graphics libraries that match your actual GPU. Omarchy ships a script for this and it is GPU aware.

   omarchy-install-gaming-gpu-lib32

   It ships on v3.8.4 and every 4.0.x snapshot. It adds lib32-vulkan-intel and lib32-vulkan-radeon for whichever Intel or AMD GPUs lspci shows, plus lib32-nvidia-utils or lib32-nvidia-580xx-utils when the NVIDIA detectors succeed, and it is the step most crash reports turn out to have skipped.

3. Check that you did not get NVIDIA userspace on a machine with no NVIDIA card. The Steam installer runs omarchy-pkg-add steam before the GPU-aware step, so pacman’s --noconfirm provider pick can win the race and pull lib32-nvidia-utils plus nvidia-utils for Steam’s lib32-vulkan-driver dependency. That is issue 8856, open as of 4.0.4.

   pacman -Qq | grep -E '^(lib32-)?nvidia'
   lspci | grep -iE 'VGA|3D|Display'

   If NVIDIA packages are present and no NVIDIA GPU is, remove them and reinstall the right driver:

   sudo pacman -Rns lib32-nvidia-utils nvidia-utils
   omarchy-install-gaming-gpu-lib32

   Reboot afterwards. The NVIDIA EGL vendor file outranks Mesa’s until it is gone.

4. Look for a leftover SDL_VIDEODRIVER. Omarchy 3.x set env = SDL_VIDEODRIVER,wayland in hypr/envs.conf (later wayland,x11), and it broke a long list of Proton titles. It was removed in v3.7.0 and it is not in default/hypr/envs.lua on v4.0.4. But it survives in personal dotfiles and in an old session environment.

   grep -rn SDL_VIDEODRIVER ~/.config/hypr/ ~/.config/uwsm/ 2>/dev/null
   systemctl --user show-environment | grep -i sdl

   Delete any line you find, then log out and back in.

5. If one specific game still dies, set a per-game launch option. Right click the game in Steam, choose Properties, then Launch Options. Try the cheap one first:

   unset SDL_VIDEODRIVER; %command%

6. If that does not do it, wrap the game in gamescope. Omarchy does not install gamescope for you, so add it first:

   sudo pacman -S --needed gamescope

   Then use a launch option shaped like this, with your own resolution and refresh rate:

   env -u LD_PRELOAD gamescope -W 2560 -H 1440 -r 165 -f -- env LD_PRELOAD="$LD_PRELOAD" %command%

   The LD_PRELOAD dance matters. A plain gamescope ... -- %command% applies Steam’s overlay library to gamescope instead of the game, which is why people report an invisible cursor and dead keyboard input inside the overlay. limehawk described that fix on issue 3971 and credited the ScopeBuddy project for the technique.

Verify it worked

Launch the game from a terminal so you can see what Steam prints:

steam -console

Then check that the right driver is actually loaded:

vulkaninfo --summary | grep -i driverName
glxinfo -B | grep -i 'OpenGL renderer'

On an AMD or Intel machine you want Mesa drivers named there, not NVIDIA. If you are on a hybrid laptop, run nvidia-smi while the game is up and confirm the discrete GPU is actually doing work.

Why it happens

Three separate problems produce the same symptom.

The historical one is SDL_VIDEODRIVER. Forcing SDL to a single backend removes its fallback chain, so any game whose SDL build cannot talk to Wayland exits instead of trying X11. RyanBreaker opened issue 2564 with a list of affected titles and pointed at the SDL documentation saying the auto-detection is the sane default. dhh first tried wayland,x11, which silenced the console warning but did not fix the crashes, and the variable was dropped entirely in the v3.7.0 “Gaming Edition” release.

The current one is driver mismatch. Steam’s 32-bit runtime needs a lib32 Vulkan driver for your card. Issue 2466 showed Intel machines where every game reported a fatal error until lib32-mesa and lib32-vulkan-intel were added by hand. Issue 8856 shows the opposite failure, where NVIDIA userspace lands on an AMD laptop because of installer ordering.

The third is hybrid laptops. default/hypr/nvidia.lua on v4.0.4 sets __GLX_VENDOR_LIBRARY_NAME=nvidia session wide whenever omarchy-hw-nvidia finds an NVIDIA GPU, with or without GSP firmware, and never consults omarchy-hw-hybrid-gpu even though that detector sits in the same bin/ directory. There is no PRIME offload wrapper anywhere in the tree. Issue 9688 documents the result: the dGPU sits at zero percent while games freeze or crawl on the iGPU. That issue is open.

If that did not work

• Native Linux builds that only launch once, such as the Paradox titles in issue 4016, were reported on 3.2.3 while SDL_VIDEODRIVER was still set. Reporters got them running again with Proton, with gamescope, or with SDL_VIDEODRIVER=x11 %command% as a launch option.
• Fullscreen flicker rather than an outright crash is issue 4595. Proton Experimental fixed it for one reporter. gamescope is the other option.
• If Steam itself never shows a window, that is a different failure. Issue 2870 in October 2025 looked like one, with dozens of same-day reports and one console log showing Failed to load steamui.so over a missing libXtst.so.6. The real culprit was an fcitx5 update (fcitx/fcitx5#1441), and the fix was the patched fcitx5 package Omarchy published to its own repo the same day. If Steam hangs right after a system update, check what pacman just upgraded before chasing driver theories.
• Controllers that Steam sees but games ignore are issue 8373, a /dev/uinput permission problem, not a crash.
• A game that seems to blink to the desktop every 150 seconds is the screensaver, not a crash. See issues 6947 and 9636.

Evidence for 4.x specifically is thinner than for 3.x. Most of the detailed crash reports predate Quattro, and the 4.0.x gaming issues in the tracker are about driver selection and idle handling rather than new crash causes.

Related

• NVIDIA drivers on Omarchy 4
• Hybrid GPU laptop black screen
• NVIDIA hardware notes and hybrid GPU notes
• Omarchy manual: Gaming