This is fixed for the next update, thanks!
We do plan to move the runtime out once we have everything set up, but there's currently no ETA.
If you want to permanently disable the steam runtime, simply add STEAM_RUNTIME=0 to /usr/bin/steam.
Cheers!
Would it be possible to silence this message when STEAM_RUNTIME=0 is set
We know that the steam runtime was not setup because it was intentionally disabled. This should be as easy as checking for STEAM_RUNTIME=1 before throwing the message.
Yep, as I said above, it's fixed for the next update.
okay, thank you for clarifying.
EDIT: I asked because #1323 is a spin-off of this bug because it was unclear.
I just got a update on Steam and got this message! :(
Edit: I started Steam from terminal and found out that some file were corrupted. I removed the corrupted files and restarted Steam. Which started to download updates and the problem was fixed! :)
Nothing extracted yet.
After today's update /usr/bin/steam no longer honors STEAM_RUNTIME=0.
As well intended as the steam runtime is, I would rather forfeit all dependency-related support on all games and the client than use precompiled libraries not intended for my setup. While packages I build on my own must pass rigorous authenticity checks, steam runtime has no such safety.
/usr/bin/steam acknowledges it received STEAM_RUNTIME=0, but does not pass it to the steam client. ~/steamdir/steam.sh accepts the variable properly.
For those who do benefit from the steam runtime, I think it would be beneficial for it to be move to a recommended support package, so that it can be updated independently from steam and because it is not strictly necessary for the client to run well. It is not an issue now with the beta and updates two to three times a week, but once it leaves beta, the gap will be much longer.
Most of all, I would appreciate if there was an opt-out option for steam-runtime, to save space and hassle, perhaps with a warning that no support will be given if it is disabled.
Gentoo Linux, 64 bit.