- cross-posted to:
- technews@radiation.party
- cross-posted to:
- technews@radiation.party
tl;dr In a recent thread on Mastodon, it was revealed that Ubuntu 23.04 users can’t install the Steam deb package from the Ubuntu archive without jumping through some technical hoops. It turns out this was a mistake, a bug was filed, and future builds shouldn’t have this problem.
Steam - the game store/launcher from Valve requires a bunch of 32-bit libraries to function. Many of the games that Steam installs also require many of these various libraries. These older games are likely never going to get updated to have 64-bit clean builds.
The thread on Mastodon brought up an expected thought process, though. The conspiracy theory-minded might (reasonably) think “This is Canonical breaking the deb, so you’re forced to use the snap”. But that doesn’t appear to be the case.
It’s just a simple mistake that is fixed, and now (a selected set of) i386 packages will be easily accessible again.
You must log in or register to comment.
Everyone should just use the flatpak. You can get the latest version, latest Mesa, latest mangohud etc on any distro and it will all work exactly the same.
I’m fine with just using the .deb .
I don’t dislike flatpak and it’s good that it exists but I prefer not using it if I don’t have to.
If you are installing the latest mesa, you want to use it when playing?
This is still a statement, even with the question mark
Thanks for posting this. I couldn’t figure out why Steam was broken on my laptop for the last 3 weeks or so. Installing the .deb from the Steam website fixed it. I’m starting to get fed up with Canonical.
Pretty sad state of affairs :|
Just install the flatpak version to add insult to that self-inflicted injury. Works pretty well for me.
I guess one question is: why is it still 32-bit? Feels like something Valve should be updating now.
I’d wonder if it is too maintain compatibility with 32-bit titles?
TL;DR is that wine doesn’t yet support WoW64 (Windows on Windows64), which enables the running of 32-bit binaries on a 64-bit system - it’s conceptually similar to multilib on Linux. You can’t run 32-bit Windows bins on a purely 64-bit WINE as I understand it.
But the Steam launcher doesn’t run on Wine. Some games may run on Proton but one shouldn’t depend on the other AFAIK?
well, Wine does support WoW64, but the way it’s implemented requires you to install both 32 and 64 bit Wine.
“Yes. Do as I say.”
This is off topic, but why is it that if I go to their download Steam web page on openSUSE, it has me download the .deb package?
deleted by creator
Presumably they just either haven’t made a proper package for opensuse, or their platform detection isn’t perfect. Since Debian based distros are the most common, sometimes companies will only distribute Deb files…
In any case, I’d personally recommend getting steam via flatpak, it works quite well.
The flatpak is what I eventually settled on, but I was a little confused initially. Upon initially installing the flatpak, I was having some minor issues, so I was going to try to see if installing it natively was any better, but there seemed to be no way to.
I eventually figured out that I really just needed to launch Steam on my dedicated GPU instead of my integrated graphics. Now it runs fine.
It used to be that everything was packaged in an RPM, now DEB runs the show.
installing i386 packages on an x86_64 install has always been more annoying than it should be.
