To ensure games run well on Linux either via Native Linux builds or Windows games with Proton, part of the magic is in the Steam Linux Runtime. A new version of it, the Steam Linux Runtime 4.0 was recently put up with some pretty big changes.

What's the point of it? It ensures Steam and games run through Steam on Linux work properly across all the many different Linux distributions. Another secret Valve sauce for Linux. Well, not secret at all but you get my meaning I'm sure.

you are viewing a single comment's thread
view the rest of the comments
[–] 10 points 11 months ago (43 children)

Funny this shows up when all of a sudden Steam won't launch anymore on my Arch install. It's installed via flatpak.

How do I even check which version of the Steam runtime I am running? The flatpak version of Steam is just 1.0.something.other.

  • source
  • hideshow 43 child comments
  • [–] 36 points 11 months ago (19 children)

    The runtime is not Steam itself. That's more or less independent from the runtime. The runtimes are a collection of libraries that developers can develop against without having to include them themselves.

    Kind of similar to the Visual C++ Runtime on Windows.

  • source
  • parent
  • hideshow 19 child comments
  • [–] 5 points 11 months ago (11 children)

    I know what a runtime is, but I'd like to check which version of it I'm running. 🙂 Wouldn't be very difficult but I'm this instance I don't know how.

  • source
  • parent
  • hideshow 11 child comments
  • [–] 12 points 11 months ago (10 children)

    The runtime is for launching games, not Steam itself. You can check the runtime selection in Compatibility tab of Steam and of each game. If your Steam Flatpak install doesn't work, the issue is likely somewhere else.

    I'd suggest trying to launch the flatpak from the terminal and seeing if there's any strange logging.

  • source
  • parent
  • hideshow 10 child comments
  • [–] 3 points 11 months ago*

    I'd suggest trying to launch the flatpak from the terminal and seeing if there's any strange logging.

    Already did that but I couldn't see anything that I could recognize as abnormal. The "Connecting" window shows up, actually. But it just stops loading for a second and then it just says "Reaping pid" in the console and it closes the process.

  • source
  • parent
  • [–] 2 points 11 months ago (8 children)

    The runtime is for launching games, not Steam itself. You can check the runtime selection in Compatibility tab of Steam and of each game. If your Steam Flatpak install doesn't work, the issue is likely somewhere else.

    Hold up, are you talking about the compatibility layer, "Proton"? I'm not sure that's what we're talking about here. Proton is up to version 9 and 10, not 4.0.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 9 points 11 months ago (7 children)

    You can select Steam Runtime Versions in the Compatibility tab too, separate from Proton versions

  • source
  • parent
  • hideshow 7 child comments
  • [–] 1 point 11 months ago (6 children)

    Oh okay, I guess that's in the main Steam settings, not per game as the other person suggested.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 4 points 11 months ago* (2 children)

    You can select it per game as well, steam runtime 3.0 and now presumably steam runtime 4.0 should show up in the same drop down menu next to proton 1.0, proton 10.0 in the compatibility options

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 11 months ago (2 children)

    No, it is a per game setting. When your game is a native Linux game it will use one of the Steam runtimes. If you had a Linux native game and selected Proton instead of a Steam Linux runtime Steam would download the Windows version of the game.

    With Linux native games you usually don't have to touch this setting.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 0 points 11 months ago* (1 child)

    Right but you can't change the native runtime per game. You can only change the compatibility layer (Proton) globally and per game. The runtime is static obviously, and either used or not used. I'm guessing Proton bypasses the native runtime by having the game interacting with it? Or maybe it is a translation layer? Both? Anyway, doesn't matter. 🙂 What wasn't the problem.

    But I'd still be interested in how to check which version I have, just to know.

    Edit: hold on, does the runtime show up in the same list as Proton versions? That would explain what you all are talking about. And only for native Linux games. That's why I haven't seen it before I guess.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 0 points 11 months ago

    The runtime is a container with libraries. Proton always runs inside the container by design. The runtime ensures the software environment is predictable, Proton ensures Windows binaries can run (by handling Windows API calls)

  • source
  • parent
  • [–] 2 points 11 months ago* (6 children)

    So you can use those to develop on a platform and be sure that it work on the other too? Is this runtime steam-indipendent?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 8 points 11 months ago (1 child)
  • [+] -2 points 11 months ago (3 children)
  • [–] 8 points 11 months ago (2 children)

    No, it's for running games on Linux. Steam will probably use the libs as well for its own functionality. But the main use is for game developers to target specific libraries so that they are independent of the user's distribution.

    And they can indeed be used outside of Steam as well. I sometimes use it to link in specific libraries for other games. @Axolotl_cpp@feddit.it

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (1 reply)
  • [+] 10 points 11 months ago (2 children)
  • [–] 5 points 11 months ago (2 children)

    i usually avoid flatpaks, especially with steam. but every now and then my non-flatpak steam borks too and won't launch on mint. 9 times out of 10 simple reboot helps, but sometimes it requires a reinstall...

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 11 months ago* (last edited 11 months ago) (1 child)

    Usually it's because Steam is still running in the background, so a simple pkill steam should close all the processes and allow it to launch. No need to reboot.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 11 months ago (3 children)

    Usually when steam refuses to launch, it's because there's some Steam process that's borked but still running. Most of the time, a simple pkill steam fixes it (yes, that includes for flstpak`).

    As mentioned down thread, the runtime isn't your problem. The runtime is what's needed for native Linux games and I think is also used by proton (not used by Steam itself), so it's kind of like proton for native games. Steam doesn't use the runtime at all to launch.

    If killing Steam doesn't work, try rebooting. If that doesn't work, try updating the flatpak. If that doesn't work, I suppose reinstall Steam.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 11 months ago (2 children)

    I think it might have been a denial of service type thing as explained in other replies. I didn't reboot or anything and it just worked fine now. All good. 👍 Thanks for all the help though.

    Almost every reply is also explaining what the runtime is. 😆 I know what it's for, guys, thanks! ❤️🙏👍

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 11 months ago (1 child)

    Glad you got it fixed. 🙂

    Almost every reply is also explaining what the runtime is.

    I boosted it up a bit for other people who come along w/ a similar concern. You seemed mistaken at first until a few threads deep, so there's likely someone else who is just as, if not more, confused.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 11 months ago* (5 children)

    You're not alone. I had the same thing on two machines yesterday. (Not flatpack)

  • source
  • parent
  • hideshow 5 child comments
  • [+] 1 point 11 months ago (4 children)
  • [–] 4 points 11 months ago (3 children)

    Why would you use flatpack for stuff natively available on pacman? Search no further, flatpack is a good way to introduce problems where there are none

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 11 months ago (2 children)

    https://wiki.archlinux.org/title/Steam#Flatpak

    🤷‍♂️ Seemed like a good way to install it. I had used the native package before but I think I tried flatpak because of some issue or another with the native version.

    It's been working great for years now so, no issues until now.

    I usually install big corporate software with flatpak if I can help it, to keep them as isolated as possible. Slack, Discord, Steam, etc. Stuff like that. 👍

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 11 months ago* (1 child)

    From that article:

    Installing Steam from Flathub/Flatpak will fix many of the issues faced on the client but will require alternative, less documented forms of troubleshooting on the long run.

    You hit the "long run" after years 😉

  • source
  • parent
  • hideshow 1 child comment