Steam Linux Runtime doesn't work on Clear Linux #345
Labels
Comments
|
Hello @sn99, starting with Proton 5.13, Proton runs inside the Steam LInux Runtime - Soldier container environment, and that's setup by Pressure Vessel. Pressure Vessel has encountered some kind of issue setting up the container. Please could you show us a log of what pressure-vessel is thinking, and exactly what happens? You can do this without involving Proton (which should make things a bit simpler) like this: and then send container.log as a gist. You can edit/censor the log if there's anything in it that you consider private, as long as it's obvious where it has been edited, for instance replacing your username with REDACTED. The SteamLinuxRuntime_soldier directory will be in one of your Steam libraries. The most likely place is ~/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier if you haven't reconfigured the installation path. |
|
conatiner.log: gist |
|
I extracted soldier manually and replaced the files and ran: The new error I get: conatiner.log: gist I have freetype Installed and even tried installing one from source following this but get the same errors |
This looks uncomfortably as though the runtime was somehow only partially unpacked, but in a different way. What is meant to happen is that it's unpacked under a different directory name, and only renamed into place after unpacking has been fully successful, so that it can never have its final name but only partially be there... but it seems there's some situation in which this can fail.
That would certainly be consistent with the Please try Then, remove the Then Also please show us what's in It might also be helpful to check against the included |
|
VERSIONS.txt All checksum report |
This seems strange. It's not directly related to the container runtime, but would seem to indicate that there is something odd going on, and will probably result in native Linux games being broken on this system. |
Something is not right here: I wonder whether this is something about Clear Linux: does it perhaps have an unusual library search path or glibc configuration? |
Ah. Does Clear Linux's If it does, then its |
|
Games like Dota2 or tf2 seem to work fine.
Clear Linux does have a different files structure so to say link I will add more when I get some more info community discussion |
|
If you have access to
Steam doesn't run native Linux games like these in a container unless you specifically ask for it, but when it uses Proton 5.13+ to run Windows games, that happens in a container. It's the container launcher that is having trouble here. |
|
Right, we need to make this file in the container be a symlink to Workaround: |
|
This won't be game-specific, but will be OS-specific. @kisak-valve, please retitle to: "Steam Linux Runtime doesn't work on Clear Linux". |
sn99
changed the title
|
@smcv It works now, thanks for the help, appreciate it |
|
That workaround is not a permanent solution, and will stop working next time SteamLinuxRuntime_soldier is updated. Please reopen this until I've landed changes in the pressure-vessel code that will make the workaround unnecessary. (... but thanks to your testing, we now know what needs to happen to solve this properly.) |
|
This should be fixed by the combination of https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/merge_requests/218 and https://gitlab.collabora.com/vivek/libcapsule/-/merge_requests/43 when they get into a release. |
|
There was an update of soldier had to repeat the last steps again |
|
Yes, as I said already, the workaround was temporary. The new beta of SteamLinuxRuntime_soldier (look for pressure-vessel version 0.20210114.0 in VERSIONS.txt) hopefully fixes this. Please could you try it on your Clear Linux system? Switching to the beta branch of SteamLinuxRuntime_soldier is the same as switching to the beta branch of a game. Please follow the same procedure as https://support.steampowered.com/kb_article.php?ref=9847-WHXC-7326, but in the properties of "Steam Linux Runtime - soldier" rather than CS:GO. |
|
It fixed it, The game launches without needing to do anything else. |
|
@kisak-valve: I think we can remove Would it be worthwhile to have a |
This has now happened. |
|
Today's Steam Linux Runtime 2.0 (soldier) and 3.0 (sniper) betas, versioned as 0.20240415.x, have a change that slightly improves compatibility with Clear Linux ( It would be useful if a Clear Linux user or developer could try these betas before they get re-released as stable, so that we can roll back the change if it causes a regression. Would you mind trying this? As a general principle, if you are interested in having the Steam Runtime work smoothly on your OS and you are technically proficient enough to swap between beta branches and send clear bug reports, it's actually better to use the betas than the stable releases. That way, if you encounter a new regression, you can report the bug, then drop back from beta to stable while waiting for it to be fixed, and less-technically-proficient users of your OS hopefully won't have to encounter the bug at all. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compatibility Report
System Information
I confirm:
Symptoms
The game does not launch in latest proton version
Reproduction
Open steam and launch game
Additional info
/etc/ld.so.cacheso I ransudo ldconfig -C /etc/ld.so.cache$PATHalready include/usr/local/bin:/usr/local/sbin:/usr/binSteam Linux Runtime - SoldierThe text was updated successfully, but these errors were encountered: