Dennis HilkLinux diagnosticsDE

Linux Gaming Repair Center

A Proton game fails to launch

Find the earliest blocking failure and separate the game, launcher, compatibility tool and host graphics stack.

Editorial source review: Open the diagnostic assistants
On this page
  1. Name the runtime before changing it
  2. Follow the failing process
  3. Protect the prefix and check title support
  4. Gather evidence
  5. A controlled test
  6. Related diagnostics
  7. Sources & limitations

Name the runtime before changing it

Wine implements Windows interfaces. Proton combines a modified Wine with graphics translation and the Steam runtime; DXVK handles older Direct3D paths and VKD3D-Proton handles Direct3D 12. Record the exact per-game Steam compatibility selection, including whether it is stable Proton, Experimental or GE-Proton. The system wine --version output does not identify Steam’s selected Proton. GE-Proton has its own support channel and requires its supported runtime outside Steam; the former Wine-GE project is archived and points to umu. A runner label alone does not reveal which prefix and libraries the launcher actually used.

Follow the failing process

Start one attempt with Proton logging and note whether the launcher appeared, a game process existed, or the failure happened before a window. Read the first relevant error together with nearby module and process messages. Repeated fixme lines are not automatically fatal. A missing import DLL, executable-format error, rejected anti-cheat initialization and Vulkan device failure lead to different investigations. For a missing dependency, establish which executable requested it and use the game’s supplied prerequisite installer or documented repair path. Random DLL downloads and a bundle of prefix changes make the next result harder to interpret.

Protect the prefix and check title support

A prefix can contain saves, launcher state, installed prerequisites and registry settings. Back it up with the game closed before any experiment that may migrate it. Verifying game files repairs managed installation files; it does not reconstruct all prefix state. If an online title stops at anti-cheat, consult its developer’s current Linux or Steam Deck statement. Valve’s support for middleware still requires configuration by the game developer. A different Proton build cannot guarantee access to unsupported servers. Report the selected tool, game build, failure stage and a reviewed, redacted log excerpt.

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.

Temporary diagnostic environment

PROTON_LOG=1 %command%

Requirements: Steam game launched with Proton; a launch-option string, not a terminal command.

Put this in the game’s Steam launch options for one attempt. The log normally appears as steam-APPID.log in your home directory. It may contain private paths; review before sharing. Remove the option afterward.

Read-only observation

file "/path/to/game.exe"

Requirements: The file utility and access to the actual game executable.

Replace the path with the executable named by the failing launcher. PE32 and PE32+ describe the Windows executable; a shell script or missing file points to another startup stage.

Read-only observation

wine --version

Requirements: Standalone Wine available in the current shell; not needed for a Proton-only installation.

Useful only when the failing game really uses this standalone Wine executable. Compare the launcher’s runner path; this output says nothing about a separate Steam Proton build.

A controlled test with a way back

Save the existing launch options, disable custom options for one baseline attempt, then add only PROTON_LOG=1. Keep the same compatibility tool and game build so the log describes the failure you are investigating.

Rollback: Restore the saved launch options. If a later test changes Proton, select the previous build; this does not undo prefix migrations. Restore a prefix backup only with all game and launcher processes closed.

What this test cannot establish: Logging can change timing and may stop before the decisive event. A startup warning without a failing process or reproducible symptom is insufficient evidence for a repair.

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.