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

Issues when using Protontricks #6

Open
62832 opened this issue May 3, 2023 · 8 comments
Open

Issues when using Protontricks #6

62832 opened this issue May 3, 2023 · 8 comments

Comments

@62832
Copy link

62832 commented May 3, 2023

Figured I'd post another issue report, though as per the accompanying email I sent regarding this I wasn't sure whether this was still in scope.

I came across a couple of issues with tools like Protontricks when the enforcer is up and running. Firstly, every installed Proton game seems to be listed twice:

image

Further to that, configuring these games does not seem to work when using the enforcer as part of the script back in #4. As an example, when trying to install the d3dx9_43 verb for BIT.TRIP CORE (app ID 205060), Protontricks simply returns the following output before hanging indefinitely:

$ protontricks 205060 d3dx9_43

protontricks (WARNING): Current Steam Runtime not recognized by Protontricks.
pressure-vessel-wrap[3727]: W: sd_journal_stream_fd: Function not implemented
pressure-vessel-adverb[3917]: W: sd_journal_stream_fd: No such file or directory
pressure-vessel-adverb[3917]: E: Failed to execute child process "/run/user/1000/steam/.steam/root/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service" (No such file or directory)
@davidebeatrici
Copy link
Member

Not out of scope at all!

This program is supposed to work with all setups involving Steam, including Proton stuff.

Could you run the enforcer in debug mode and send here the output, please?

@62832
Copy link
Author

62832 commented May 3, 2023

This'll take me a while, looks like I nuked half my Steam installation by accident and have to restore a couple things before I can get back to you.

In the meantime, could I just clarify again what to look for? Would anything involving that exact Steam runtime path be the thing to keep an eye out for in the debug log?

@davidebeatrici
Copy link
Member

Pretty much. Once you find the line(s), you can just scroll up to check whether there are other relevant ones.

@62832
Copy link
Author

62832 commented May 3, 2023

Managed to get the following:

[fs_getattr] /root/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service
[fs_getattr] /root/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-HBCD41/usr/lib/pressure-vessel/from-host/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-HBCD41/usr/lib/pressure-vessel/from-host/bin/steam-runtime-launcher-service
[fs_link] /root/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service
[fs_link] /root/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-HBCD41/usr/lib/pressure-vessel/from-host/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-HBCD41/usr/lib/pressure-vessel/from-host/bin/steam-runtime-launcher-service
...
[fs_getattr] /root/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service
[fs_getattr] /root/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-QZUV41/usr/share/X11/locale/iso8859-14 -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-QZUV41/usr/share/X11/locale/iso8859-14
[fs_getattr] /root/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-I8LU41/usr/lib/pressure-vessel/from-host/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-I8LU41/usr/lib/pressure-vessel/from-host/bin/steam-runtime-launcher-service
[fs_link] /root/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service
...
[fs_getattr] /root/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service
[fs_getattr] /root/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-QZUV41/usr/lib/pressure-vessel/from-host/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-QZUV41/usr/lib/pressure-vessel/from-host/bin/steam-runtime-launcher-service
[fs_link] /root/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/pressure-vessel/bin/steam-runtime-launcher-service
[fs_link] /root/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-QZUV41/usr/lib/pressure-vessel/from-host/bin/steam-runtime-launcher-service -> /extra/_/Games/Steam/steamapps/common/SteamLinuxRuntime_sniper/var/tmp-QZUV41/usr/lib/pressure-vessel/from-host/bin/steam-runtime-launcher-service

Since the full log, even after only about half a minute of runtime, was about 100MB in size, I've uploaded the rest of it here.

@davidebeatrici
Copy link
Member

I checked the relevant lines in the full log and didn't spot any obvious issues, I would check with ltrace which call is returning an error for the specific path.

@62832
Copy link
Author

62832 commented May 4, 2023

I can't say I've ever used ltrace before so I can't guarantee a very quick response to where any errors are occurring. I'll see what I can do later today.

@davidebeatrici
Copy link
Member

Were you able to gather info through ltrace?

@62832
Copy link
Author

62832 commented May 6, 2023

Afraid not, I haven't gotten around to that yet and it seems a bit above my level of expertise. Sorry.

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