Hello @ermonski, Tool 1628350 "Steam Linux Runtime 3.0 (sniper)" unsupported version 0. and Tool 2805730 "Proton 9.0-4" unsupported version 0. look like lines of interest in your compat_log.txt. This tells us that these tools are damaged or incomplete. Most current era Proton builds run inside the Steam Linux Runtime 3.0 container environment, so if that's unhealthy, then anything that uses it can't run.
I'd verify the integrity of the tool's files in the per-game properties for the runtime and Proton. If that doesn't help, then I'd check if they ended up on a secondary Steam library folder that's on a non-Linux-native filesystem.
Hello @ermonski,
Tool 1628350 "Steam Linux Runtime 3.0 (sniper)" unsupported version 0.andTool 2805730 "Proton 9.0-4" unsupported version 0.look like lines of interest in your compat_log.txt. This tells us that these tools are damaged or incomplete. Most current era Proton builds run inside the Steam Linux Runtime 3.0 container environment, so if that's unhealthy, then anything that uses it can't run.I'd verify the integrity of the tool's files in the per-game properties for the runtime and Proton. If that doesn't help, then I'd check if they ended up on a secondary Steam library folder that's on a non-Linux-native filesystem.
Thanks! I changed to Proton 10-28 and The game kinda launched. How can I ree-download the other Proton versions for my other games in case they need it? I tried using other Proton versions and the error pops up so I am not able to verify the integrity of the compatibility tool files
Just faced a similar issue today. I was testing different Linux runtimes in some games (all beta_client) and at some point all the files at $XDG_CACHE_HOME/Steam/steamapps/common/SteamLinuxRuntime vanished. Steam wouldn't redownload the files nor let me to reinstall the runtimes, file validation would always pass with 0/0 and I wasn't even allowed to switch between branches (public vs beta_client). Eventually I tried removing the steamapps/appmanifest_{1070560,1391110,1628350,4183110}.acf files, which allowed be to pick branches, but made Steam stuck at downloading the runtimes.
I was finally able to recover with steamcmd +login <username> +app_update 1070560 validate +quit (and 1391110, 1628350, 4183110). So, yeah, if anyone eventually finds itself in a similar situation, SteamCMD might be useful.
proton 9.0-4x2 2026-01
Your system information
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]Please describe your issue in as much detail as possible:
Describe what you expected should happen and what did happen. Please link any large code pastes as a Github Gist
Steps for reproducing this issue:
steam-logs.tar.gz