Closed ntBre closed 1 week ago
Hello @ntBre, this issue is already being tracked at https://github.com/ValveSoftware/steam-runtime/issues/702 and Proton is not involved in this specific issue.
Closing as a duplicate.
Ah makes sense, thank you! Sorry for the noise. I didn't realize Steam had so many packages on GitHub, this is great!
Compatibility Report
System Information
I confirm:
I also tried submitting a support request through Steam since I'm not sure this is a Proton-specific issue, but the response I got redirected me here.
Symptoms
Slay the Spire suddenly fails to launch through Steam but runs fine by invoking the executable directly through the command line. stderr for Steam reports this exception:
I'm on Arch Linux and have been playing StS fine for months. I hadn't updated my Arch Linux computer in a couple of weeks and played StS two days ago, but I saw Steam update when I first opened it today and then the game wouldn't launch. Other games are working fine, but StS won't launch either as a native game (as I usually play) or through the couple of Proton versions I tested (experimental, and the most recent numbered version). After encountering an issue, I did update my Arch packages and restarted both my computer and Steam multiple times to no avail.
In searching this error message, I found that some people reported needing to install
xrandr
, but I definitely havexrandr
installed and use it to set up my displays in my.xinitrc
. I also tried removinginfo.displayconfig
as suggested here, as well as modifying it with various values. I also tried changing the resolution after opening the game from the command line, both using the normal executable andSlayTheSpireTroubleshoot.sh
. Finally, I tried settingXDG_SESSION_TYPE
tox11
as suggested here, but that also didn't work. I didn't try setting it in my.xinitrc
or anything, but I tried addingXDG_SESSION_TYPE=x11
as a launch option and setting it when invokingsteam
.Reproduction
Try to open Slay the Spire on the most recent version of Steam on Linux.
I hope this is the right place to report this. I know much of my debugging sounds like this is a game-specific issue, but the fact that it happened immediately after the Steam update and that the game launches fine without Steam makes me think it's some kind of Steam issue. Let me know if you need any more information!