this post was submitted on 20 Nov 2025
496 points (99.6% liked)

Linux Gaming

22180 readers
810 users here now

Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.

This page can be subscribed to via RSS.

Original /r/linux_gaming pengwing by uoou.

No memes/shitposts/low-effort posts, please.

Resources

WWW:

Discord:

IRC:

Matrix:

Telegram:

founded 2 years ago
MODERATORS
monolalia@lemmy.world
496
Valve put up a new Steam Linux Runtime 4.0 with a move towards 64-bit (www.gamingonlinux.com)
submitted 1 day ago by cm0002@no.lastname.nz to c/linux_gaming@lemmy.world
75 comments fedilink hide all child comments
 

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
[–] sugar_in_your_tea@sh.itjust.works 2 points 11 hours ago (1 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.

[–] victorz@lemmy.world 2 points 10 hours ago (1 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! ❤️🙏👍

[–] sugar_in_your_tea@sh.itjust.works 2 points 9 hours ago* (last edited 9 hours ago) (1 children)

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.

[–] victorz@lemmy.world 1 points 6 hours ago

Cool, yeah, no worries. 🫶 I hope someone finds it helpful!