i386 in Ubuntu won't die
popey.com
(yet) 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. It’s not immediately apparent whether the (currently ‘broken’) ISO images for Ubuntu 23.04 will be rebuilt (unlikely) or if this will stay broken in 23.

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.

  • hottari@lemmy.ml
    6·
    1 year ago

    You are clearly wrong as Ubuntu disabling x32 apps here is what caused the problem. If a distro as big as Ubuntu could never be trusted to test Steam, what chance does your distro X have?

    I do not trust people uploading Flatpaks for distribution to cover those things (even, or perhaps especially, if it’s software they’ve developed—the number of blind spots developers can have about their own environments is terrifying).

    All this flies out of the window when it’s your distro that’s introducing the bugs as was the case here.

    “Why does [preference X] not work inside this Flatpak?” is not an uncommon topic.

    This is legit and I have to give you this. It’s not perfect but to me, can’t ever recall a time a workaround was not available. Most of the time, you’ll find an issue like a plugin that is hardcoded to call to a library using the standard distro path or something like that.

    But more users catch this stuff and share solutions to the Flatpak community.