please god let the client have a 64 bit wayland edition coming
this post was submitted on 20 Nov 2025
546 points (99.5% liked)
Linux Gaming
22254 readers
483 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:
- Linux Gaming wiki
- Gaming on Linux
- ProtonDB
- Lutris
- PCGamingWiki
- LibreGameWiki
- Boiling Steam
- Phoronix
- Linux VR Adventures
Discord:
IRC:
Matrix:
Telegram:
founded 2 years ago
MODERATORS
They have to do it for steamos ig
The version of Wayland I'm running on bazzite right now is 32-bit? No wonder I'm having issues with 2 4K monitors lol
the steam client doesn't use wayland and is 32-bit, don't think that has anything to do with your monitors though
That's a good sign, that Valve is moving at least the runtimes to 64bit only. Maybe that means the client is under similar scrutiny internally. Recently when Fedora was discussing dropping more 32bit libraries Steam came up as a big issue.
Yeah, 32bit is why I removed Steam from my Debian desktop daily driver again. I got conflicting 32bit and 64bit versions of some libraries that broke my system. I'm going to try a gaming focussed distro like Bazzite next time.
???
Debian separates out stuff with :[arch] suffixes, and is really flexible in the sense that it even lets you install stuff from completely different architectures for, for example, use with qemu userspace. An i386 package is going to only request i386 dependencies, unless it explicitly specifies an architecture, and vice versa. Arch Linux uses the "lib32-" prefix and I don't really remember how it worked on Fedora but I would imagine something similar. All "gaming focused distros" are merely just their mainstream counterparts with an extra repo for a few packages, it's not going to change fundamentals.
OpenSUSE is the same, the 32-bit stuff is completely separate from the 64-bit stuff, so you won't get conflicts between them.
Give Steam Flatpak a try on Debian instead.
I've been using LMDE for the past couple years and I do all my non-switch gaming on it.
i recommend LXQT over LXDE cause its like the spiritual succesor,i think lighter and it has Wayland
but you can use whatever you like
I'm not using either of those. I'm using the LMDE default, Cinnamon.
sure
load more comments
(1 replies)
Didn't they already announce they're going to drop 32 bit?
Hey mild necro after a week, but it seems to be happening already. The new beta is 64bit! https://lemmy.ca/post/55858408
For windows at least, but I assume they'd do it across the board at once
load more comments
(2 replies)
Proton-GE has had the Wow64 feature for a while now that can play older 32-bit titles under 64-bit, so it shouldn't be long before a truly 64-bit steam experience is available.
load more comments
(3 replies)
does it say which team fortress 2 class it's named after?
From the gitlab repositories it kind of looks like they are dropping that naming scheme wit v4. It was kind of cute, but also confusing if you have no idea about TF2 and use Steam.
Steam Linux Runtime 4 (Saxton Hale)
/s
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.
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.
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.
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.
load more comments
(10 replies)
load more comments
(8 replies)
the flatpak version is unsupported by Valve for a reason. there's been a ton of problems over the lifespan of the flatpak. it's usually highly recommended everywhere not to use that version.
I've been using Steam in a flatpak for a couple years now, I think. What ton of problems are you referring to?
load more comments
(6 replies)
load more comments
(2 replies)
Install warehouse. It gives you all the details of which runtime is in a Flatpak and even lets you change the version.
I did not know about Warehouse. Thank you.
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.
load more comments
(3 replies)
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...
load more comments
(2 replies)
load more comments
(11 replies)
Any news about an aarch64 version?
The new VR headset runs ARM, so presumably it'll launch with that.
load more comments
(1 replies)
view more: next ›