How to Fix Steam Crashing on EndeavourOS

May 1, 2026-Last Updated: May 17, 2026

If you’re running EndeavourOS, the Arch-based Linux distribution known for its simplicity and rolling-release model, you might occasionally encounter a frustrating Steam crash. One moment you’re ready to game, the next Steam freezes or vanishes without a clear explanation. Before giving up on your Linux gaming setup, know that most Steam crashes on EndeavourOS stem from a handful of common causes: missing 32-bit libraries, graphics driver hiccups, or conflicts with the Steam runtime environment. This guide will walk you through every step you need to get Steam running smoothly again.

Common Causes of Steam Crashes on EndeavourOS

Steam on Linux relies heavily on 32-bit compatibility libraries, even when your system is 64-bit. EndeavourOS, like Arch, does not enable the multilib repository by default, which means many 32-bit packages are missing. Another frequent culprit is the graphics driver – NVIDIA users often face issues with kernel module loading or missing 32-bit driver components. Finally, the Steam client itself bundles many libraries in its “runtime” environment, but system updates can sometimes break compatibility, requiring you to switch to the native system libraries or use specific launch options.

System Checks: Libraries and Dependencies

Before diving into complex fixes, make sure your system has all the essential packages. Open a terminal and verify that the multilib repository is enabled. Edit /etc/pacman.conf and uncomment the [multilib] section and the Include line beneath it. Save, then update your system:

sudo pacman -Syu

Now install the base set of 32-bit libraries that Steam needs:

sudo pacman -S steam lib32-systemd lib32-libgl lib32-gcc-libs lib32-libx11 lib32-libxcb lib32-libxdamage lib32-libxext lib32-libxfixes lib32-libxinerama lib32-libxrandr lib32-libxrender lib32-libxi lib32-libsm lib32-libice lib32-libxcomposite lib32-libxcursor lib32-libxft lib32-libxscrnsaver lib32-libxtst lib32-libxxf86vm lib32-mesa lib32-mesa-demos lib32-vulkan-intel lib32-vulkan-radeon nvidia-utils lib32-nvidia-utils

This command covers most libraries, but adjust the Vulkan and NVIDIA packages according to your hardware. If you use AMD, replace nvidia-utils lib32-nvidia-utils with vulkan-radeon lib32-vulkan-radeon. After installation, reboot or restart the display manager.

Graphics Driver Issues

Graphics drivers are a top source of Steam crashes. For NVIDIA GPUs, confirm the proprietary driver is loaded:

lsmod | grep nvidia

You should see entries like nvidia, nvidia_drm, etc. If not, follow the EndeavourOS NVIDIA installation guide. Also ensure you have the 32-bit driver components installed: lib32-nvidia-utils and lib32-opencl-nvidia (if needed). For AMD users, the open-source drivers should work out of the box, but you can verify that the amdgpu kernel module is loaded:

lsmod | grep amdgpu

Intel integrated graphics typically require no additional steps, but installing lib32-mesa and lib32-vulkan-intel is still smart.

After updating drivers, it’s wise to regenerate your initramfs and kernel image with:

sudo mkinitcpio -P

Then reboot. You can also try launching Steam with the -vgui flag to rule out GPU-accelerated client rendering problems.

Steam Runtime and Launch Options

Steam ships with its own runtime environment (the “Steam Runtime”), which includes many libraries. Sometimes this runtime clashes with newer system libraries. To force Steam to use your system’s native libraries instead, launch Steam with:

STEAM_RUNTIME=0 steam

If that helps, you can make it permanent by editing the Steam desktop entry or creating an alias. Alternatively, some issues are solved by switching to the older “Steam Linux Runtime – Soldier” container. You can enable it per game by right-clicking the game in your library, choosing Properties, and under Compatibility, forcing a specific Steam Play tool.

For games that crash immediately, try adding common launch options in the game’s properties. For example:

PROTON_USE_WINED3D=1 %command%

This forces the use of Wine’s own Direct3D implementation instead of DXVK, which can bypass Vulkan-related crashes. Other helpful options include PROTON_LOG=1 %command% to generate a log file, or VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json %command% to explicitly set the Vulkan ICD for AMD GPUs.

Troubleshooting Specific Games

Some games have well-known quirks on Linux. Check the ProtonDB website for your game and read community reports. Common fixes include adding WINEDLLOVERRIDES="mfplat=n,b" for media foundation issues, or using custom Proton builds like Proton-GE. To install Proton-GE, you can use an AUR helper like yay:

yay -S proton-ge-custom-bin

Then restart Steam and select it from the game’s Compatibility tab. Also, verify the game’s integrity in Steam: right-click → Properties → Installed Files → Verify integrity of game files.

Advanced Solutions and Workarounds

If crashes persist, try launching Steam from a terminal and watch the output for error messages. Look for lines containing Segmentation fault, Could not load library, or Failed to initialize Vulkan. These clues will point you to the missing piece.

Another step is to reset Steam’s configuration by moving the ~/.steam/steam or ~/.local/share/Steam directory to a backup and letting Steam regenerate it. You can also try the Flatpak version of Steam, which sandboxes all dependencies and can bypass system-level breakage:

flatpak install flathub com.valvesoftware.Steam

However, Flatpak Steam may have limited access to external drives, so use it only if the native version proves problematic.

For users who dual-boot or use NTFS partitions, ensure the partition is mounted with proper permissions. A common fix is to mount with the exec,uid=1000,gid=1000 options in /etc/fstab.

Finally, consider creating a dedicated X11 configuration to avoid Wayland-related crashes. In /etc/gdm/custom.conf (if using GDM), uncomment #WaylandEnable=false to force X11, or simply choose an X11 session at login.