Dennis HilkLinux diagnosticsDE

Linux Gaming Repair Center

A game will not start on Steam Deck

Inspect the per-game compatibility tool, installed game variant, storage and supported SteamOS workflow.

Editorial source review: Open the diagnostic assistants
On this page
  1. Record the supported baseline
  2. Separate one game from a system failure
  3. Keep SteamOS image management intact
  4. Gather evidence
  5. A controlled test
  6. Related diagnostics
  7. Sources & limitations

Record the supported baseline

Record SteamOS update channel, installed update state and the game’s selected compatibility tool before experimenting. Confirm that downloads and required updates completed and that enough free space exists on the relevant filesystem. A native Linux build and a Windows build through Proton are different tests; forcing Proton can change which game installation Steam downloads. Start with the title’s current Steam Deck compatibility details and any developer notice. The presence of anti-cheat middleware support does not mean this specific title or its online mode is enabled.

Separate one game from a system failure

If one game fails but another supported game starts, preserve the failing game’s log and compatibility selection. If multiple previously working titles fail after an update, record the shared change and restart through the normal system controls. An external microSD library introduces its own mount and I/O path; available space on the internal drive does not establish space on the card. Desktop Mode can expose launcher dialogs that Gaming Mode hides, but a successful desktop launch changes the session context and is not a universal fix.

Keep SteamOS image management intact

Use Steam’s file verification, per-game settings and supported SteamOS updates before operating on the system image. SteamOS has a read-only system image, and unmanaged package changes can disappear on later updates. Generic Arch instructions to run pacman upgrades or disable read-only protection are not a gaming repair recipe for the Deck. Install diagnostic tools only through a supported path suited to the task. Before changing Proton, back up local saves and the relevant prefix; switching back can leave migrations behind. Keep any third-party plugin changes separate from the first comparison.

Gather evidence before changing the system

Run one command at a time in the relevant host or game environment. Read its requirements and interpretation first. The website displays commands and never runs them.

Read-only observation

cat /etc/os-release

Requirements: Steam Deck Desktop Mode terminal; read-only.

Record the installed OS identification from Desktop Mode. It does not reveal all Steam client, Proton or game versions.

Read-only observation

df -h

Requirements: Desktop Mode terminal; identify the relevant mount instead of assuming a device name.

Check the filesystem containing the game and the internal data filesystem. Free space elsewhere cannot satisfy that filesystem’s requirements.

Temporary diagnostic environment

PROTON_LOG=1 %command%

Requirements: Steam launch options for a game actually using Proton; remove after one attempt.

For the Windows/Proton variant, collect one startup log. A native Linux game does not gain a Proton log from this variable.

A controlled test with a way back

Save the original per-game settings, remove custom launch options and compare one logged launch with the current supported compatibility choice. If title-specific guidance calls for a different tool, back up prefix and saves before that separate comparison.

Rollback: Restore the saved compatibility selection and launch options. Restore backed-up prefix state only with the game and launcher closed. Use SteamOS-supported recovery guidance for an actual system regression.

What this test cannot establish: Deck compatibility details and developer support can change. These checks do not promise anti-cheat support or authorize system-image package replacement.

Sources and scope

This editorial review uses primary project and distribution references. It does not establish that a fix has been reproduced on your hardware. Installed versions, the game runtime and the selected graphics API can change the result.