Skip to content
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

soldier_protonfixify fails with "No such file or directory" #164

Open
saintdev opened this issue Jul 30, 2021 · 1 comment
Open

soldier_protonfixify fails with "No such file or directory" #164

saintdev opened this issue Jul 30, 2021 · 1 comment

Comments

@saintdev
Copy link

Describe the bug
Attempting to run soldier_protonfixify fails with:

$ soldier_protonfixify .local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/ .local/lib/python3.7/site-packages/protonfixes
cat: .local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier//com.valvesoftware.SteamRuntime.Platform-amd64,i386-soldier-buildid.txt: No such file or directory

The file in fact does not exist:

$ ls .local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/
pressure-vessel/                .ref                            run-in-soldier                  _start-container-in-background  _v2-entry-point                 VERSIONS.txt                    
README.md                       run                             soldier_platform_0.20210629.0/  toolmanifest.vdf                var/

This seems to happen when attempting to set the BUILD_ID variable.

To Reproduce
run soldier_protonfixify script

Expected behavior
script should not error with No such file or directory

Logs
No logs other than above

Operating System:

  • Distro and Version: Solus 4.3
  • Proton Version: Proton 6.3

Additional Information
I just updated steam after not having access to this computer for a while and it just downloaded the soldier runtime, so this is a brand new runtime install.

@ThisNekoGuy
Copy link
Contributor

Happens by default just by running install_protonfixes too:

Example
install_protonfixes
Protonfixes already installed in /home/neko-san/.local/share/Steam/compatibilitytools.d/proton_tkg_7.19.r0.g41a3c56c.ASYNC-Staging-futex_waitv, skipping
Protonfixes already installed in /home/neko-san/.local/share/Steam/compatibilitytools.d/proton_tkg_7.19.r0.g41a3c56c.Staging-futex_waitv, skipping
Installing protonfixes in /home/neko-san/.local/share/Steam/compatibilitytools.d/proton_tkg_7.22.r0.gd8881486.ASYNC-Staging-futex_waitv
Protonfixes already installed in /home/neko-san/.local/share/Steam/compatibilitytools.d/proton_tkg_experimental.bleeding.edge.7.0.27190.20221017.ASYNC-Valve, skipping
Protonfixes already installed in /home/neko-san/.local/share/Steam/compatibilitytools.d/proton_tkg_experimental.bleeding.edge.7.0.27190.20221017.Valve, skipping
Soldier runtime detected, patching it
cat: /home/neko-san/.local/share/Steam/steamapps/common/SteamLinuxRuntime_soldier/com.valvesoftware.SteamRuntime.Platform-amd64,i386-soldier-buildid.txt: No such file or directory
Not sure how significant this issue is; I don't know why the soldier runtime would need to be patched?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants