Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
Linux

Bazzite Would Shut Down If Fedora Goes Ahead With Removing 32-Bit (gamingonlinux.com) 61

If Fedora drops 32-bit support, the gaming-focused Bazzite project would be forced to shut down, according to its founder Kyle Gospodnetich. "As much as I'd like this change to happen, it's too soon," said Gospodneitch in a post. "This change would kill off projects like Bazzite entirely right as Fedora is starting to make major headway in the gaming space. Neal Gompa already pointed out basic use cases that would be broken even if someone built the packages Steam itself needs to function."

He continued: "It's also causing irreparable damage to Fedora from a PR standpoint. I have been inundated all day with people sharing news articles and being genuinely concerned Steam is gong to stop working on their Fedora/Bazzite machines. I would argue not only should this change be rejected, the proposal should be rescinded to limit further damage to Fedora as a project. Perhaps open a separate one to talk about changing build architecture to build fewer 32-bit packages?"

When pushed further, Gospodnetich said: "I'm speaking as it's founder, if this change is actually made as it is written the best option for us is to just go ahead and disband the project."
This discussion has been archived. No new comments can be posted.

Bazzite Would Shut Down If Fedora Goes Ahead With Removing 32-Bit

Comments Filter:
  • I don't know a lot about this project but I am not understanding why they wouldn't just move to a non-Fedora based distribution. There are *LOTS* of them.

    • The whole point is that Bazzite is the Red Hat-based gaming distro. If Bazzite used another distro, it would really be something else entirely and likely be somewhat duplicated effort.

      What I don't get is why they can't do their own packaging of 32 bit libraries? I assume that what Bazzite devs do is mainly packaging, so why not also package this thing that your distro needs to work?

      • If that is the whole point, they could mention that on their https://bazzite.gg/ [bazzite.gg] page? I can't seem to find it....

        • I guess they don't say it like I did, but there are about 8 references to Fedora on their site, they're clearly based on Fedora.

      • by Tony Isaac ( 1301187 ) on Wednesday June 25, 2025 @08:05PM (#65476630) Homepage

        There's no technical reason to lock their platform to Fedora. If they are that tightly coupled to Fedora, they should rethink their design. Linux is the platform, software should target Linux, not just one distro.

        • by thegarbz ( 1787294 ) on Thursday June 26, 2025 @05:21AM (#65477224)

          They are not some program running on Linux. They are an entire self contained distro. Yes in the Linux world many distros are very tightly coupled to their upstream parent projects. If Ubuntu disappeared tomorrow you wouldn't lose one distro; about 20 others would close up. This is precisely why everyone lost their shit when Debian adopted SystemD - the downstream effects of this were huge.

          It's not trivial to simply migrate your distro to a different parent project. It's a monumental task, and having your entire project break in this way would be hugely demotivating.

           

          • While your points are correct, they also reinforce my point. If you are building something for Linux, don't hitch your wagon to a single distro. Fedora and Debian aren't so special that downstream projects must be tightly coupled to them.

            The software development community is learning the importance of decoupling. Dependency injection, interfaces, microservices, containers, while overused in some contexts, are still examples of an important principle. Tightly-coupled systems are more fragile than loosely cou

            • While your points are correct, they also reinforce my point. If you are building something for Linux, don't hitch your wagon to a single distro.

              You don't seem to understand how downstream distributions work. The alternative here is to roll your own distro from scratch. That is a monumental effort in its own right and those who do it successfully have a big team of developers working for them.

              The entire open source movement is built on hitching your wagon to something someone else built. Even simple things like library dependence, or the choice of which GUI framework to build your project in is dependent on someone else. This decoupling rant you're

              • I get it. My question is, why did this system *have* to be a distro? There are plenty of gaming platforms that run as an app, you know, like Steam for Windows. I doubt that the features of Bazzite inherently require it to BE a distro.

                Anyway, they made their choice, there's no going back, and it seems, there may be no going forward.

                • I get it. My question is, why did this system *have* to be a distro?

                  Same reason SteamOS is a distribution. Linux gaming even now in 2025 requires a lot of finely tuned parts working in unison. If you think it's like Windows where you install Steam and call it a day, you're going to have a very bad time.

                  Managing compatibilities between various compatibility layers like Proton, drivers (still a shitshow to install on a normal distro thanks in part to the anti-binary anti-open source limitations), and then tuning it all so it works somewhat cohesively (no end user likes spendi

                  • Same reason SteamOS is a distribution

                    Steam actually does run on Windows, Mac OS, Android, and iOS. Most Steam users use these platforms, and I'm pretty sure they're not all having a "very bad time." Steam (unlike Bazzite) hasn't hitched its existence to a single distro. Nor did they force support for 32-bits.

              • Also, even if it was necessary to *be* a distro, if apparently their distro modification process is broken.

                If you start with a distro, and can apply your modifications automatically, you'd be in a position to switch distros. This is similar to how you set up Docker containers: you start with a base, and add your customizations to that base. If you do that, and the base changes, then your customizations can easily be applied to the changed base (in this case, a changed parent distro). If instead you create a

          • by allo ( 1728082 )

            Then maybe they need to shut down the project and start a new one. Debian will probably still support 32 Bit in 20 years.

            • Then maybe they need to shut down the project and start a new one. Debian will probably still support 32 Bit in 20 years.

              Read the last sentence I wrote.

    • by Burdell ( 228580 )

      Building a Linux distribution requires a fair amount of infrastructure, and that's something that's pretty different from distro to distro (and not all make all the necessary tooling public). Changing to a different base distro would most likely require a significant rework, and may be more than someone, especially someone who has mastered the intricacies of one distro's tooling, wants to do.

      • They could just use Yocto to handle building their distribution. Granted that customization of a Yocto distribution can sometimes be mildly painful, but once setup shouldn't be too hard to maintain.
    • Re: (Score:3, Informative)

      by keitosama ( 990483 )
      Bazzite is based not on the regular Fedora but rather the Fedora Silverblue distribution, which is an immutable/atomic operating system built on top of rpm-ostree. Maybe the Bazzite team could create something similar from a NixOS base instead, but they really would have to start their work all over from scratch (as far as making an OS fork fits that wording).
    • by devloop ( 983641 )

      I don't know a lot about this project but I am not understanding why they wouldn't just move to a non-Fedora based distribution. There are *LOTS* of them.

      Or fork Fedora, right?

    • by fr ( 185735 )

      Bazzite is part of the Universal Blue Project which are a handful of official images and also the base for custom images, they would have to duplicate the work from that project if they switch to something else.
      Also, one of the main components for the system is "rpm-ostree" which is obviously rpm only but also seems to be quite Fedora centric.

    • One limiting factor is that Bazzite, Aurora and Bluefin are all based on Fedora SilverBlue, which is an atomic distribution, rather than standard Fedora. This is by design.

      I'm not part of the project, so I don't know if it could be quite a major to move to another underpinning atomic distribution of similar quality.

    • This person is delusional.

      The whole parent project is at the intersection of cloudy devops and Linux desktop woo woo

    • He means through Bazzite itself, which is steadily growing its install base by being very SteamOS-like but with the maturity, flexibility and massive repos that Fedora brings to the table. Just jump on YouTube and search for Bazzite, it's getting hyped for being a "Windows killer" for gaming and "better SteamOS than SteamOS".

      Its momentum isn't nothing and it would be a shame for it to die over an arbitrary decision from a member of the Fedora engineering team. He's not wrong, of course - at some point 32-bi

  • by sirotocus ( 61730 ) on Wednesday June 25, 2025 @06:26PM (#65476418)

    Is this person not aware of the 10000 other distributions? If this project is solely to play games on fedora and somehow not any other distribution then I doubt it is any great loss. And if you can't make changes so that it runs on another distro then I have a hard time believing the project does anything useful because you would have to be incredibly dense.

    Perhaps it is vibe coded and they need to get on the AI's good side to get these changes done or whatever.

  • Slackware (Score:5, Interesting)

    by packrat0x ( 798359 ) on Wednesday June 25, 2025 @07:07PM (#65476526)

    Slackware is the stable distribution they're looking for.

    • EXACTLY what I was going to say, my good sir!

      Good to see a fellow Slackware user in the wild :)

    • By default, a Slackware x64 install doesn't support 32 bit either. If you need to run 32 bit software, you have to install multilib support yourself.

      • By default, a Slackware x64 install doesn't support 32 bit either. If you need to run 32 bit software, you have to install multilib support yourself.

        True. But Multilib [slackware.com] is unlikely to be yanked from Slackware, making it LTS viable.

  • After all, the steam client on Mac is 64 Bit, and porting from BSD-ish to Linux should be relatively easy, dobly so because the Steam client is based on chromium which has both 32 and 64 bit clients.

    Granted, Valve took their Sweeeeet time moving the Mac Client from 32 to 64 bits, but hey, it was doable....

    • RIP TF2 Mac client.
    • It's not that weird. Much of what Steam sells won't run as expected without some amount of 32 bit support(you are much less likely to find that the main game is 32 bit for anything that got a cross platform release with an 8th gen console, since all but the switch had more than 4GB of RAM; but absolutely no promises on every config launcher or random middleware component); and the steam client itself has, thankfully, remained comparatively lightweight. Probably not as light as it could be; but on the speedi
    • by Touvan ( 868256 )

      MacOS dropped 32-bit a few years ago, and it did the same thing - murdered gaming dead, on macOS. It's actually easier to run Windows 32-bit binaries on macOS than it is to run 32-bit macos binaries. MOST of my macos compatible Steam library doesn't work any more. (And it'll be so much worse when the remove Rosetta 2 - and they will, bet.)

      What would make sense to me, is to create some kind of hybrid virtualization/containerized thing to run old binaries (think something like WPA2.) Hybrid binaries might be

  • by williamyf ( 227051 ) on Wednesday June 25, 2025 @07:40PM (#65476590)

    Bazzite based on Fedora:

    Take inspiration from linux mint. Mint is based of Ubuntu, but they also have a Linux Mint Debian Edition for the sole purpose of validating that, if needed be because ubuntu does something they do not agree with, they can move to debian and keep operating.

    Maybe is time to do the same. Rebase the project on another distro. Not necesarily Debian, but something more tenable for your purposes.

    • Ubuntu is based on Debian, so obviously is easier to change from Ubuntu to Debian than from Fedora to Debian. Also, probably is a difference in the number of contributors.

  • by williamyf ( 227051 ) on Wednesday June 25, 2025 @07:44PM (#65476600)

    Fedora's raison d'etre (sorry for the lack of accents), is to be a testing ground of the future evolution of RHEL, I believe that, by the time RHEL11 lands, the RHEL ecosystem will not need 32bit libraries or executables for that matter.

    So, better not waste the scant resources RH destines to Fedora in making 32 bit happen. Instead, lobby Valve to move the steam client from 32 to 64Bits.

    JM2C YMMV

    • by Anonymous Coward

      RHEL may WANT to go 64bit only, but their enterprise customers will tell them 32bit library layers stay or RH can fuck right off since they won't port their old stuff to 64.

      Enterprise moves at glacial speeds. It's all about stability. They aren't going to rewrite, if they even CAN, everything to 64 bit "just because". They will just pay support to someone else and tell RH to go pound sand.

      • They already did it.... RHEL 10 removes all 32bit multilib/library packages from the OS. If you need 32bit libraries, you're stuck with RHEL 9.

  • According to distrowatch, the last 32 bit version was Fedora 25 in 2017. Apparently this means that Fedora would also stop providing 32 bit libraries that are frequently available for 64 bit Linux systems.
    • Re:Not clear (Score:4, Informative)

      by caseih ( 160668 ) on Wednesday June 25, 2025 @08:49PM (#65476698)

      They are referring to multiarch support (as debian calls it). The OS itself is 64-bit, but all the infrastructure to run older 32-bit binaries (including win32 exes on Wine) is available in the repos. Fedora has always packaged 32-bit rpms even right up until Fedora 42.

      Now in this case they are referring to Fedora Silverblue, not the normal rpm-based distro everyone knows about. Obviously Silverblue has some kind of 32-bit multiarch support, which Fedora is planning to eliminate.

  • Should have switched to Debian a decade ago. Redhat is the walking dead.

  • If more distros gave 32-bit the chop, Valve would be forced to adopt 64-bit, and everyone would rejoice. Therefore, I'm all for this change. That's my art-of-the-deal 4D chess analysis.
  • All 32bit libraries/multilib functionality was completely removed in RHEL10, having been deprecated in RHEL 9.

    6.11. Compilers and development tools
    32-bit packages have been removed in RHEL 10
    Linking against 32-bit multilib packages has been removed. The *.i686 packages remain supported for the life cycle of Red Hat Enterprise Linux 9.

    This is likely a move to align Fedora in the same direction since Fedora -> CentOS Stream -> RHEL

Harrison's Postulate: For every action, there is an equal and opposite criticism.

Working...