Game does not start (Proton 7.0-4). Tried completely uninstalling and reinstalling, and the symptoms are the same: it shows a window saying "Completing installation" that stays around for about 5 minutes, then pops up a dialog saying "The Steam server are too busy to handle your request for Saints Row: Gat out of Hell. Error Code (55)".
Tried during the whole day today, along with a hundred other games which worked, including Saints Row II, III and IV. Using PROTON_LOG=1 %command% does not even generate the steam-301910.log file. There seems to be no errors on the recent logfiles under ~/.local/share/Steam/logs.
Game is still not starting in Proton. I've noticed that when set to Proton 7.0-4 or any other proton, the file steam_appid.txt is never there.
Game starts natively but only the intro -- and then it crashes, also crashes if using Steam Linux Runtime, with an eON error (wine-like layer from Virtual Programming) (attached file)
gat-out-of-hell-crash-report.txt
Natively, the game has an steam_appid.txt file. Changing from native to proton-7.0-4 makes the steam_appid.txt file disappear from the game's directory. And then trying to run the game shows this on the console:
GameAction [AppID 301910, ActionID 30] : LaunchApp changed task to UpdatingDRM with ""
A few seconds pass then a window appears:
The Steam servers are too busy to handle your request for Saints Row: Gat out of Hell. Error Code (55)
and these new lines appear on the terminal:
src/clientdll/clientjobrequestcustombinary.cpp (670) : eResult != k_EResultRemoteCallFailed
src/clientdll/clientjobrequestcustombinary.cpp (670) : eResult != k_EResultRemoteCallFailed
GameAction [AppID 301910, ActionID 30] : LaunchApp failed with UpdatingDRM with "55"
GameAction [AppID 301910, ActionID 30] : LaunchApp changed task to Failed with ""
Note that the game is broken for other people too, latest protondb reports are all failures, including on the Steam Deck. Please fix this game! https://www.protondb.com/app/301910
Nothing yet? Has anyone been able to run this game lately?
still doesn't work, from proton/native version.
Hi friends,
i hope i can help a bit. I buyed the game today from steam store, then i tried to start it, but nothing worked (no window apeared).
After some gambling with different proton version i gave up and tried another path, i added the "SaintsRowGatOutOfHell.exe" as external Program to Steam and tried it that way with PROTON_LOG=1 enabled ofc and ProtoExperimental as layer, then i got a lot of debug output (see for yourself).
steam-14696616365905674240.log
i added the steam_appid.txt to the game folder under steamapps/common/.... and removed the gamemoderun from the commandline. now it looks a bit more clear. it seems the process tries to connect to a RPC endpoint but that fails for unknown reason or it doesn't work as usual.
here the new logfile...
steam-301910.log
4405.167:0064:0070:warn:seh:dispatch_exception RPC_S_SERVER_UNAVAILABLE exception (code=6ba) raised
seems harmless according to issue https://github.com/ValveSoftware/Proton/issues/7610 .
now i try a bigger logfile, with PROTON_LOG=+relay,+x11drv,+vulkan,+winediag
the new dump is 166Mb large. that's why is compessed with xz tool.
compessed with xz -vk9z steam-301910.log, you can uncompress with xz -vd steam-301910.log.xz
have fun with investigation ;)
congrats for your attempt, but this issue has been quiet for years now. I hope the new data you brought for diagnostics help in some way, but I doubt it will. DRM executables weren't supposed to be run as external programs.
In any case, I tried to run it with Proton 9.0 (Beta). Same symptom: I press play, it grinds the HDD a bit saying "updating executable", nothing happens. It doesn't generate steam-301910.log.
But according to https://www.protondb.com/app/301910 it works (not with the steam version right now), but with the GOG version. I don't think they are so different from each other, iam not an expert, but pretty sure its trivial and fixable.
Just be more patient LOL
The game (and others) runs using the Flatpak version of Steam (on any distribution)
As i mentioned previously, first of all happy new year!!! second, this game can be launch using the native Flatpak Steam is able to launch the game Steam Linux runtime (native Linux version of the game) but it is MANDATORY to run it with the FLATPAK VERSION OF STEAM since the original/pre-installed version of steam doesn't recognize the launcher executable as sh and the system by default it is not-readable the system can't synchronize dependencies between the OS (Steam-OS) and the Game on files, Flatpak version runs at what it looks like at any type of distributions so automatically switches to FLATPAK dependencies instead of In-System dependencies, as i mentioned you previously i hope this resolutions could solve potentials interferences when you try to play more steam decks games on the future :D
That's useful to know, unfortunately I refused to run steam as flatpak. But thanks for the info, if I ever feel the need to run that game I'll create a new user just for the flatpak steam.
Proton doesn’t load is just stuck on "updating executable"
using "PROTON_LOG=1 %command%" fails to generate a log i'm going to try and see what’s going on
The previous fix submitted using the exec find on <Link removed by moderator> has been able to play the game without any issue, personally didn't work first try, what you need to do it that's happens will need to restart you PC then try and will be able to open up after that "updating executable" thing appear, not further actions are needed the game just open up and runs as supposed to.
Hello @ElPinguino99, the workaround you linked is legally problematic and has been removed.
it's okay np
proton 9.0x1 2024-04proton 7.0-4x2 2022-11PROTON_LOG=1x3 2025-06PROTON_LOG=+relay,+x11drv,+vulkan,+winediag`x1 2024-04
Compatibility Report
System Information
I confirm:
[x] that I haven't found an existing compatibility report for this game.
[x] that I have checked whether there are updates for my system available.
steam-301910.log
Symptoms
When launching the game it simply doesn't spawn a window or anything. Nothing really happens and it eventually crashes.
Reproduction
Simply launch the game