How to Fix Steam Games Not Launching on Linux Mint (2026 Guide)

Why Steam Games Won't Launch on Linux Mint

If a Steam game won't launch on Linux Mint, the cause is usually one of six things: a Snap or Flatpak Steam install, missing 32-bit libraries, a missing Vulkan driver, a Proton version mismatch, NTFS mount permissions, or a corrupted shader cache or Proton prefix. This guide fixes each one in order, starting with the quickest, and most users are back in the game within the first two or three steps.

The symptoms are familiar. You click Play, the button flickers green for a moment, then nothing happens, or the game crashes back to the library instantly. Sometimes Steam shows the game as "Running" without ever opening a window. In 2026 this is still one of the most common complaints from Linux Mint gamers.

The root causes fall into a handful of categories:

• Proton/Wine compatibility layer errors — the Windows-to-Linux translation layer hits a missing dependency or version mismatch
• Missing 32-bit libraries — Steam still depends heavily on 32-bit packages even on 64-bit systems
• Vulkan / GPU driver issues — games using Vulkan/DirectX 12 fail silently when the right driver or Vulkan loader is absent
• NTFS drive mount problems — games stored on a Windows-format (NTFS) drive can't execute because of wrong mount permissions
• Wrong Steam installation method — Snap or Flatpak versions of Steam are sandboxed and break Proton for many games
• Outdated or missing Proton version — the default Proton bundled with Steam may be too old for a specific game

Work through the methods in order. Each one is quick to test, and you can stop as soon as your game starts.

Before You Start: Enable Proton for All Games

If you have never enabled Steam Play (Proton) globally, do this first — it is the single most common reason non-native Linux games refuse to launch.

1. Open Steam and click Steam → Settings → Compatibility
2. Toggle on Enable Steam Play for all other titles
3. Set the Proton version to Proton Experimental or the latest stable release
4. Restart Steam

If Steam Play was already enabled, continue to Method 1 below.

Method 1 — Reinstall Steam the Correct Way

The Snap and Flatpak versions of Steam are sandboxed in ways that prevent Proton from accessing system libraries. If you installed Steam from the Software Manager or via snap install steam, this is very likely your problem.

Remove the Snap or Flatpak version

sudo snap remove steam
# OR for Flatpak:
flatpak uninstall com.valvesoftware.Steam

Install the official .deb package from Valve

# Enable 32-bit architecture first
sudo dpkg --add-architecture i386
sudo apt update

# Download and install Steam's own .deb installer
wget https://repo.steampowered.com/steam/archive/precise/steam_latest.deb
sudo apt install ./steam_latest.deb

# Launch Steam (it will self-update on first run)
steam

After Steam self-updates and you log in, try launching the problem game again. This alone fixes the issue for the majority of users who installed Steam through the Software Manager. Your existing game library is not deleted when you remove the sandboxed version if it lives in a separate folder, but back up any custom library location before you begin.

Method 2 — Install Missing 32-bit Libraries and Vulkan Drivers

Even after a clean Steam install, launching a game may produce a black flash and immediate exit if key 32-bit or Vulkan packages are missing from your system.

Install 32-bit support and Vulkan packages

sudo dpkg --add-architecture i386
sudo apt update
sudo apt install   libgl1-mesa-dri:i386   libgl1:i386   mesa-vulkan-drivers   mesa-vulkan-drivers:i386   libvulkan1   libvulkan1:i386   vulkan-tools

Verify Vulkan is working

vulkaninfo --summary

If the command returns adapter information for your GPU, Vulkan is working. If it errors, your GPU driver is the problem — continue to Method 4.

For NVIDIA users, also install

sudo apt install libnvidia-gl-535:i386

Replace 535 with your installed NVIDIA driver version (check with nvidia-smi). The 32-bit library version must match the installed driver branch exactly, otherwise Vulkan games will still fail to start.

Method 3 — Fix the Proton Version for the Specific Game

Some games work with one Proton version but crash with another. The game's Steam page on ProtonDB usually lists the version that community members report as working.

Install Proton-GE (community-patched Proton)

Proton-GE includes extra codecs and patches that the official Proton lacks. Many games that crash on official Proton launch fine with Proton-GE.

# Install ProtonUp-Qt to manage Proton versions
pip3 install protonup-qt
# OR install the flatpak version:
flatpak install flathub net.davidotek.pupgui2

Open ProtonUp-Qt, click Add version, select GE-Proton, and install the latest release. Then in Steam:

1. Right-click the game → Properties → Compatibility
2. Tick Force the use of a specific Steam Play compatibility tool
3. Select GE-Proton from the dropdown
4. Close and launch the game

Add a debug launch option to identify the crash

Right-click the game → Properties → General → Launch Options and paste:

PROTON_LOG=1 %command%

After attempting to launch, a log file named steam-APPID.log appears in your home folder. Open it and search for err: or ERROR lines — they reveal exactly what is failing. Remove the launch option once the game runs, because logging slows the game down and the log file grows quickly.

Method 4 — Fix GPU Driver and PRIME Issues

On laptops with dual GPUs (Intel integrated + NVIDIA or AMD discrete), games may launch but immediately crash, or simply show a black screen, because Steam is trying to run the game on the wrong GPU.

Check your current GPU driver status

# For NVIDIA:
nvidia-smi

# For AMD:
glxinfo | grep "OpenGL renderer"

Install or update the NVIDIA proprietary driver

sudo apt install nvidia-driver-535 nvidia-settings

Or use the graphical driver manager: Menu → Driver Manager and select the recommended proprietary driver. The Driver Manager is the safer option because it picks the driver branch that Linux Mint recommends for your card; the 535 above is only an example, so use a newer recommended branch if one is listed.

Force a game to use the NVIDIA GPU (PRIME offload)

Right-click the game → Properties → General → Launch Options:

__NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia %command%

Switch NVIDIA to Performance mode system-wide

sudo prime-select nvidia

Log out and back in. This disables Intel iGPU output and routes everything through the NVIDIA card — far better gaming performance and eliminates many crash-on-launch bugs caused by GPU switching.

For AMD hybrid laptops

DRI_PRIME=1 %command%

Add the above to the game's Launch Options to run it on the AMD discrete GPU.

Method 5 — Fix Games Stored on an NTFS Drive

If your Steam library is on a drive formatted as NTFS (common when dual-booting with Windows), Proton cannot execute game files because NTFS by default mounts without execute permissions on Linux.

Check which filesystem your drive uses

lsblk -f

Look for ntfs or ntfs3 in the FSTYPE column next to your drive.

Fix NTFS mount options

Open Menu → Disks. Select the NTFS drive, click the cog icon on the partition, then Edit Mount Options. Add the following to the end of the mount options string:

,uid=1000,gid=1000,rw,user,exec,umask=000

Unmount and remount the drive (or reboot), then try launching the game again. If Windows was shut down using Fast Startup, the drive may still mount read-only, so disable Fast Startup in Windows if the options above have no effect.

Alternatively, edit /etc/fstab directly

sudo nano /etc/fstab

Find the line for your NTFS partition and change the options field to:

uid=1000,gid=1000,rw,user,exec,umask=000,nofail

Save and run sudo mount -a to apply.

Method 6 — Clear Steam Shader Cache and Corrupted Files

A corrupted shader cache or broken game files can cause a game to show "Running" for a second then exit with no error message.

Verify game file integrity

1. Right-click the game in Steam → Properties → Local Files
2. Click Verify integrity of game files
3. Steam will re-download any missing or corrupted files

Clear the shader cache

rm -rf ~/.steam/steam/steamapps/shadercache/APPID

Replace APPID with the game's Steam App ID (visible in the URL on the game's Steam store page). This forces the shader cache to rebuild on next launch.

Delete and recreate the Proton prefix

rm -rf ~/.steam/steam/steamapps/compatdata/APPID

Steam will create a fresh Wine/Proton prefix the next time you launch the game. You will lose any game saves stored inside the prefix (most modern games sync saves to Steam Cloud, so this is usually safe). If a game does not use Steam Cloud, copy the prefix folder somewhere safe before deleting it.

Advanced Fix — Enable GameMode for Better Performance

GameMode is a daemon from Feral Interactive that temporarily optimises CPU governor, I/O scheduling, and GPU performance profile when a game is running. It can also resolve crashes caused by power-saving features throttling the CPU mid-game.

sudo apt install gamemode
# Verify it is working:
gamemoded -t

Add gamemoderun %command% to the game's Launch Options to activate it automatically per game.

If you need expert help diagnosing a persistent Linux Mint gaming issue, CloudHouse Technologies Pay-Per-Ticket Support connects you with a Linux specialist who can remotely diagnose your specific system — no subscription required.

Frequently Asked Questions

Why does Steam show a game as "Running" but nothing opens on Linux Mint?

This happens when the game process starts but crashes before creating a window. The most common causes are a missing Proton prefix, broken 32-bit libraries, or a shader cache corruption. Delete the compatdata folder for that game (~/.steam/steam/steamapps/compatdata/APPID), verify file integrity, and add PROTON_LOG=1 %command% to Launch Options to see the exact crash reason in the log file.

Do I need to enable Proton for every game individually on Linux Mint?

No. Go to Steam → Settings → Compatibility and enable Steam Play for all other titles. This applies Proton to every non-native game automatically. You can still override the Proton version on a per-game basis via the game's Properties page.

What is Proton-GE and should I use it on Linux Mint?

Proton-GE (GloriousEggroll) is a community-maintained fork of Valve's Proton that includes extra media codecs, Wine patches, and DXVK/VKD3D updates not yet merged into official Proton. Many games that crash or show blank cutscenes on official Proton work correctly on GE-Proton. Install it via ProtonUp-Qt and try it when the official Proton fails.

Can I run Steam games from an NTFS hard drive on Linux Mint?

Yes, but you must fix the mount options first. By default NTFS partitions mount without execute permissions, which prevents Proton from running game binaries. Add uid=1000,gid=1000,exec,umask=000 to the NTFS mount options in Disks app or /etc/fstab. After remounting, Steam games on that drive will launch normally.

My NVIDIA laptop freezes when gaming on Linux Mint — what should I do?

Freezes on NVIDIA hybrid laptops are usually caused by PRIME on-demand mode switching under load. Run sudo prime-select nvidia to lock the system to the NVIDIA GPU, then log out and back in. Also add __NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia %command% to the game's Launch Options. Install gamemode and use gamemoderun %command% to prevent CPU throttling during gameplay.