protonscr

[beta] client 1729208001 downloads scout & soldier runtimes upon launch of non-native Proton-based titles

steamopen Steam client
ValveSoftware/steam-for-linux#11360 · opened 2024-10-19 by tgurr · updated 2024-10-25 · 4 comments · github
1 matching comments, n / p to jump
Ttgurr 2024-10-19 github

Your system information

  • Steam client version (build number or date): 1729208001 / Fr., 18. Okt. 1:14 UTC -08:00
  • Distribution (e.g. Ubuntu): Exherbo Linux
  • Opted into Steam client beta?: Yes
  • Have you checked for system updates?: Yes
  • Steam Logs: -
  • GPU: AMD RX7800XT (mesa)

Please describe your issue in as much detail as possible:

1729208001 / Fr., 18. Okt. 1:14 UTC -08:00 releate notes stated:

Linux

  • Steam developers can now select which Steam for Linux runtime to use for native titles. Please consult the partner site for more details.
  • Native titles will execute in 'Steam for Linux runtime 1.0 (scout)' by default, instead of the legacy runtime environment.
    This behavior is consistent with Steam Deck and promotes better compatibility across all Linux desktop distributions.
    Note that this new feature can be turned off globally with "-compat-force-slr off" on the Steam client command line.

However when launching a non-native Proton-based game, in my case "Warhammer 40,000: Darktide" which worked fine and started right away now steam first downloaded the 1.0 scout runtime, failed to start the game, after closing it and trying to run it again it now also downloaded the 2.0 soldier runtime and afterwards Proton / the game started fine.

Is this expected? Previously I had only the 3.0 sniper runtime installed and it was enough to run non-native Proton-based games.

Note I'm on Proton Experimental (experimental-9.0-20241016).

Steps for reproducing this issue:

  1. Launch a non-native Proton-based game
  2. See steam client beta now also downloading 1.0 scout and 2.0 soldier runtime first upon starting a Proton-based game
TTTimo 2024-10-21 github

Hello,

You should only need sniper for running modern Proton. I agree this doesn't sound like expected behavior. Do you mind providing your steam logs? (generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs)

Also make sure the steam play setup didn't get globally disabled in case it's the same issue as https://github.com/ValveSoftware/steam-runtime/issues/698

Ttgurr 2024-10-21 github

You should only need sniper for running modern Proton. I agree this doesn't sound like expected behavior. Do you mind providing your steam logs? (generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs)

Requested logs: steam-logs.tar.gz

Also make sure the steam play setup didn't get globally disabled in case it's the same issue as ValveSoftware/steam-runtime#698

Looking good I guess:
Bildschirmfoto_20241021_184101

However it's hard for me to reproduce the initial report as Steam doesn't allow me to deinstall/remove scout & soldier runtimes, trying to do so yields an error:

Bildschirmfoto_20241021_184349

I do also have some native games installed though, like Stardew Valley for example maybe that's the reason why Steam doesn't allow me to remove the runtime(s) now? Forgot to mention that in my initial report, maybe Steam does some magic detecting them and that's the reason why the runtimes got downloaded and installed in the first place, though like in the initial report stated it happend when launching a game using Proton (I didn't launch any native game since the update arrived).

TTTimo 2024-10-24 github

Unfortunately these logs were truncated and do not carry any useful information. I can't confirm that a Proton title launch would have triggered the installation of scout and soldier SLR.

The changes in 1729208001 do however enable scout SLR for native titles, (and scout SLR depends on soldier SLR). I suspect one of your native titles updated, and that triggered the install of scout and soldier, which are needed now.

Ttgurr 2024-10-25 github

I'm pretty sure I already installed any available updates and downloads Steam had to offer beforehand at that point before launching the Proton title so I'd carefully rule out the case that a native title got updated in the same run.

Thanks for the feedback, since you can't reproduce the issue and I'm currently unable to test again due to not being able to uninstall the 1.0 & 2.0 runtime and noone else showed up having a similiar issue feel free to close this issue, if I'm able to reproduce the problem in the future and it still persists for me I can reopen it.

Proton versions

Upstream links