this post was submitted on 27 Aug 2023
114 points (99.1% liked)

Linux

48090 readers
743 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
114
Why the Steam deb from Canonical has been broken since 23.04 (popey.com)
submitted 1 year ago by pnutzh4x0r@lemmy.ndlug.org to c/linux@lemmy.ml
28 comments fedilink hide all child comments
 

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 are viewing a single comment's thread
view the rest of the comments
[–] nyan@lemmy.cafe 10 points 1 year ago (1 children)

Brace yourself for the punchline: I don't even use Ubuntu, and what I said is not specific to any distro. Making sure that packages work, and work properly, is the single most important job a distro does.

Correct integration matters to me. Testing by someone trusted matters to me. I trust my distro's dev team to do those things. 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). "Why does [preference X] not work inside this Flatpak?" is not an uncommon topic.

Anyway, I can confidently say that the number of users whose PCs have Windows on them and not Linux approaches 10/10 too. There's a reason argumentum ad popularum is a fallacy.

[–] hottari@lemmy.ml 3 points 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.