Hello @radgeRayden, your Proton log looks like https://github.com/ValveSoftware/steam-for-linux/issues/9586.
Hello @radgeRayden, your Proton log looks like ValveSoftware/steam-for-linux#9586.
I can confirm I have the same issue on other games albeit only when I try to open the overlay itself, such as Factorio (which I believe is native opengl).
Having same issue. The game did crash sometimes when loading but performed alright afterwards. However, all out of sudden it also started crashing when opening overlay.
Running fine on Proton Experimental
Had been running perfectly with Proton Experimental, but the game suddenly stopped being able to launch at all. Fails with other Proton versions, even after full system and drivers update, game reinstall, Steam reinstall, and Vulkan test.
Hello @rrosener, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.
Risk of Rain Returns fails to start on Linux with Proton Hotfix
Issue transferred from https://github.com/ValveSoftware/SteamOS/issues/1870.
@Oblomov posted on 2025-04-10T02:53:19:
Additional information that may be relevant:
Debian GNU/Linux trixie/sid (64 bit)
Kernel Name: Linux
Kernel Version: 6.12.17-amd64
X Server Vendor: The X.Org Foundation
X Server Release: 12101016
X Window Manager: awesome
Steam Runtime Version: steam-runtime_1.0.20250307.120442
Driver: AMD AMD Radeon Graphics (radeonsi, rembrandt, LLVM 19.1.7, DRM 3.61, 6.12.17-amd64)
Driver Version: 4.6 (Compatibility Profile) Mesa 25.0.3-1
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x1002
DeviceID: 0x1681
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 3840 x 2160
Primary Display Size: 13.54" x 7.64" (15.51" diag), 34.4cm x 19.4cm (39.4cm diag)
Primary VRAM: 512 MB
(NOTE: I also have an NVIDIA dGPU, but this is not used by X11, although it is available for compute.)
When I try to launch Risk of Rain Returns on Linux using Proton Hotfix, it fails with Wine giving the error in the attached message box:
Win32 function failed: HRESULT: 0x80004005
Call: at line 234 in file \Graphics_DisplayM.cpp
Note that it worked without any issues until April 7. Still works correcting when using Proton 9.0-4
Additional information: my system is running Debian Sid. The Steam Linux Runtimes (scout, soldier, sniper), Proton, and Steamworks Common Redistributables are installed on the local disk. All games (including RoRR) are installed on an external storage accessed via FS.
Since all RoRR information is being collected here, I will add that when it runs, the intro and final films play without audio, while the game itself plays audio correctly.
Recent updates to the Proton 9.0 branch seem to have made the game unplayable again. No error message this time, but the game window fails to appear even after waiting for several tens of minutes. Running with PROTON_LOG=1 gives a very barebone file:
======================
Proton: 1742490093 proton-9.0-4e
SteamGameId: 1337520
Command: ['/oneforall/games/steam/oblomov/steamapps/common/Risk of Rain Returns/Risk of Rain Returns.exe']
Options: {'forcelgadd'}
depot: 3.0.20250306.120299
pressure-vessel: 0.20250225.0 scout
scripts: 0.20250225.0
sniper: 3.0.20250306.120299 sniper 3.0.20250306.120299
Kernel: Linux 6.12.21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.21-1 (2025-03-30) x86_64
Language: LC_ALL None, LC_MESSAGES None, LC_CTYPE None
Effective WINEDEBUG: +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree
======================
Hello @Oblomov, a header only Proton log hints that something went awry before the game itself had a chance to start. If you completely close Steam, then run steam from a terminal, is there a hint in the terminal spew when you tell Steam to start the game?
Can confirm that as of the time of this writing, I can confirm that the intro animation has no sound, however the game is running flawlessly with default proton in the most recent Nobara Linux release as well as on my OLED Steam Deck. Wonder if what people are seeing is distro-dependent.
Hello @kisak-valve thanks for the feedback. It seems indeed to be a bit unreliable. Sometimes it starts, sometimes it doesn't. Restarting steam does seem to help when it fails to start, but since it's a bit random it's hard to be sure.
Concerning the audio for the intro movie, audio plays for the first second or so and then it cuts off on my machine now.
On the SteamDeck, it seems that the intro animation audio plays fully.
I have come back to RoRR after some time without playing, and it seems that recent Steam/Proton/RoRR updates have broken it. The file produced by PROTON_LOG=1 spams a huge amount of syscall fault backtraces.
I'm attaching here the first lines of the log produced by Proton Hotfix.
======================
Proton: 1746128130 hotfix-20250501
SteamGameId: 1337520
Command: ['After this, the last messages keep repeating forever, potentially producing several tens of GBs of text log always with the same repeated syscall fault.
@Oblomov is that happening on your Steam Deck still or on a desktop? I've recently played on a desktop running Bazzite as well as my steam deck using the default recommended proton and haven't experienced any more animation nor crashing issues.
@Oblomov you shouldn't use proton hotfix, do you see the issue with other proton versions? Like 9, 10, or experimental?
Since the latest update (1.1.0) the game has been unable to properly link to Steam. It assumes my user ID is 0 and my name is Player.
Since saves are stored by user ID, this resulted in the game completely forgetting about my save until I manually copied my save.
While the game is still playable, this completely breaks achievements and likely multiplayer as well.
Interestingly, if I move the Steam API DLLs out of the game files, and try to start the game, it doesn't care at all and still runs. The game might not even be looking for them in the right place?
Downpatching to 1.0.5 confirms it is new with 1.1.0.
The Steam API files in 1.1.0 are larger than the ones in 1.0.5, and swapping them out for the ones in 1.0.5 also doesn't crash.
Hello @Bottinator22, with the current game release, please add PROTON_LOG=1 %command% to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)
...ah
line 1225:
[STEAMWORKS]: Debug: steam_appid.txt file not found.
let me add one, see if it fixes this
Added one to the game's install folder and it just... deletes it?
[STEAMWORKS]: Debug: steam_appid.txt file deleted successfully.
I will note in both cases my Steam API version is SteamClient022 while (according to the log) the game seems to want 021
[STEAMWORKS]: Failed to init Steam. No SteamClient021
For reference, this is a log from 1.0.5
SteamClient021 should be provided by SteamWorks 1.59 which is in Proton 9.0 and newer (https://github.com/ValveSoftware/Proton/commit/43417291003238ace752c7d83b791d86776ae060). Your Proton log tells us you're using Proton 8.0. Please reconfigure Steam to use a newer Proton version and retest.
It appears that works. Thought I tried that. Guess I didn't.
proton 9.0x2 2025-09proton 8.0x1 2025-09proton hotfixx3 2025-07proton 9.0-4ex1 2025-05proton 9.0-4x1 2025-04proton experimentalx2 2024-01PROTON_LOG=1x2 2025-09PROTON_LOG=1`x2 2025-06WINEDEBUGx2 2025-06advapi32.dllx1 2025-06bcrypt.dllx1 2025-06cabinet.dllx1 2025-06combase.dllx1 2025-06comctl32.dllx1 2025-06coml2.dllx1 2025-06crypt32.dllx1 2025-06dbghelp.dllx1 2025-06dnsapi.dllx1 2025-06gdi32.dllx1 2025-06imagehlp.dllx1 2025-06imm32.dllx1 2025-06iphlpapi.dllx1 2025-06kernel32.dllx1 2025-06kernelbase.dllx1 2025-060xc0000005x1 2025-060x80004005x1 2025-04
Compatibility Report
System Information
I confirm:
Symptoms
Game doesn't open most of the time (to be more precise, it opens into the loading screen then crashes). When playing I also get 50fps sometimes even though my machine is more than capable of running the game.
Reproduction
Just try to open the game. It's possible that the issue only occurs after fullscreen is selected in the game options.
Update: the issue goes away if the steam overlay is disabled for this game.
steam-1337520.log