-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
non-steam shortcuts that use proton do not update dependent compatibility tools when starting #7664
Comments
FYI: This happens on 20.04 as well clean install. This game plays fine with Wine / Lutris though.. |
Did you edit the properties for the game and configure it to use some version of Proton? The latest/default one should be fine, but you don't mention having done that step. |
I have tried it both ways. I set it to each of them in 5.x and experimental and no luck. Still failed to open. Same errors, though. |
Do you have steam games that use Proton, do they work? Let's make sure that part is working fine before looking at non steam games. |
I do have 1, Airport CEO, it wasn't working but it seems to work ok now after I recently did a fresh install. |
Sims 4 is available on the Steam store. I'm guessing you have a non Steam version of it, and you can't switch to using the Steam version instead? |
Hello @Treverr, have you configured the non-steam game to use a compatibility tool in the per-game properties or in the global Steam settings? If you have changed the per-game settings, what is it set to? (Right click on the non-steam game in Steam's Library view -> Properties -> Compatibility on the sidebar.) |
@TTimo - correct I have a non steam version of it @kisak-valve Yes, I have. I have configured it both in the global settings and then also tried to set it on the game specifically. I have tried experimental and then all the 5.x releases, and they all do the same thing. |
@Treverr please provide pressure vessel logs (https://github.com/ValveSoftware/steam-runtime/blob/master/doc/reporting-steamlinuxruntime-bugs.md#essential-information) and proton logs (https://github.com/ValveSoftware/Proton#runtime-config-options) if you still experience problems. Based on you having at least some proton steam games working, I suspect this is going to be a Proton issue rather than pressure vessel, possibly specific to TS4 .. we'll see. |
I enabled |
I tried running it via the "older" method doing
And all it gave me was:
|
Hello @Treverr, did you close Steam before running it from a terminal? That looks like it saw that Steam is already running and quit. |
Sorry that was my mistake, it wasn't completely closed. Logs are:
|
Is the distro-modified Steam package intercepting stderr and putting it somewhere like |
Not seeing
There are no proton logs outputting to my home dir either, just that pressure one. Would the dumps be helpful? |
Hello. Any ideas on what the next step might be? |
Shortcut launch failed (non-steam game) Issue transferred from #7772. Your system information
Please describe your issue in as much detail as possible:I play few games outside of steam with proton. I know this might not be a very common use-case, but hey, it works. At least it did until today. For no apparent reason some of my shortcuts (i.e "Add a non-steam game to library") stopped working. I get an error message "Steam - Shortcut launch failed. Failed to launch Name Of The Game". I was using steam beta (must have opted-in way back when because I didn't even remember that). Tried regular Steam, still the same problem. Tried to create another shortcut, still the same problem. Interestingly enough, another shortcut for a different game works just fine. Here's what I see in the terminal when I press Play on such a shortcut:
Negative appID seems strange, doesn't it ? Looking at the compatdata directory I see that the failing game got an appID 2332010280. At first I thought it must be a problem with an int overflow, but the other game that doesn't fail to launch has an even bigger ID... Steps for reproducing this issue:
EDIT: I figured out a "fix". If you go to the Compatibility tab for the affected shortcut and uncheck "force a specific version" and then try to launch the game, it won't give you this error. Although the game won't launch either. Then you can go back, select the proton version you want and the game works again. |
This happens because non-steam shortcuts do not support dependencies on compatibility tools, so the shortcuts are being started without any dependency checks and then fail. The steam client will provide more detailed error information when this and similar situations happen moving forward. Until the steam client supports dependencies for non-steam shortcuts, a workaround is to start a steam game that uses steamplay configured with the same proton version as your non-steam shortcut, or to manually install the needed compatibility tools ("Proton 6.3" and "SteamLinuxRuntime - soldier" for instance). |
I'm also having this issue. None of the non-steam games are launching now. The last time I remember it was working was around 5 months ago. Running either non-steam Windows games with Proton or Linux games would work anymore. |
Same issue here. Can't launch any non-steam game. Ubuntu 20.04. |
This started happening to me today. The non-steam windows games were playing fine through Proton. Then I tried installing the Epic Games Launcher. At first it created an AppID and everything in the .local/share/steam/steamapps/compatdata folder, it launched just fine also. Then when I quit it and tried to re-launch it, it failed. So I tried to remove the app, including the proton prefix associated with the specific appid in the compatdata folder. That is when everything stopped working. Including the previously working non-steam windows games. |
Just got this issue today, how do I fix this? |
I'd like to add that I'm seeing the same behavior on non-Proton shortcuts with the Mar 31, 2022 Steam Beta build. Took a random Linux executable from /usr/bin offered by "Add a Game" (Evince, in this case) and upon hitting "Play" it gets stuck at "Updating Document Viewer", showing "Ready to launch" and a checkbox next to If it's relevant, "Clearing Download Cache" from Steam's settings had no effect. |
I managed to track down the issue of not being able to launch any non-Steam program, incl. native binaries from /usr/bin down to missing Proton v5.13 in my case. I've no idea why v5.13 was relevant in launching a generic Linux binary and as far as I can tell, of the two Proton-using games I had installed, neither used Proton v5.13. I found out about Proton v5.13 being the issue from ~/.local/share/Steam/logs/content_log.txt printing out the following as I was launching native Linux binaries:
Why Steam attempted and failed to write to some library with a blank path is beyond me. Manually installing Proton v5.13 worked fine, as did launching and installing Steam games. |
I discovered in a reddit thread that someone else's steam was throwing the error because it was trying to find a different version of proton that wasn't installed. My fix was to install all versions of proton. I then discovered after that my default steam play proton was set to proton 7 vs experimental (which is what I had for the shortcut to launch. tl;dr try downloading all proton available versions |
I just ran into this as well and was able to resolve it by installing Steam Linux Runtime - Soldier via terminal. |
No cake for me. The log did not yield any helpful information. Deleted the Steam Linux Soldier Runtime and verified the files, and then restarted the Steam client. The interesting thing is that the overlay is available when starting a game, alt-tab is working but not screenshots, and then it dies off and become unavailable altogether. |
Your system information
Please describe your issue in as much detail as possible:
When adding a non-steam game it fails to launch.
Steps for reproducing this issue:
error.log:
Crash logs:
assert_20210218163323_28.dmp.zip
The text was updated successfully, but these errors were encountered: