We may potentially be in for some big changes in Fedora 44, with plans in place being discussed to drop 32-bit multilib / i686 packages.
I hope they remember what happened when Canonical planned the same for Ubuntu, when Valve jumped in to note they would no longer recommend Ubuntu and then Canonical backtracked on it. Linux distro developers may not like it, but Steam is huge and requires 32-bit to work properly for the client and for Proton / Wine.
This is only a proposed change for Fedora 44 onwards, it has not yet been approved. They're having a vote on the Fedora Forum where the change is being discussed. Even if it's approved, Steam wouldn't be the only problem, there's no doubt various other apps, tools and games that would break with such a huge change. At least with the Wine 9.0 release, WoW64 saw a huge improvement for running 32bit games on a full 64bit system.
The Fedora developers do at least note in the proposal that Wine and Steam are part of the dependencies on this, so they are thinking it through and aware of the issues.
Changes like this might push Valve to move a little quicker to adapt Steam to full 64bit, but I wouldn't expect anything ready any time soon. Especially when you look at Valve's own stats where Fedora doesn't even register in the top 11 distributions used on Steam. Although, we don't know what distros make up the 7% for the Steam Flatpak - but that's not supported by Valve anyway.
What are your thoughts?
Update 12:52 UTC - in response to some replies on their forum, the developer who proposed the change made it clear that eventually it will have to happen:
This is why it’s a proposal, and why I filed it more than 6 months earlier than strictly required.
But just to clarify - we will need to drop support for 32-bit x86 at some point. It’s dead, and more and more software just doesn’t support being built and / or run in 32-bit environments at all.
Yes, some things will stop working. But I hope that we can provide solutions and / or workarounds for most use cases.
And it’s better to start planning for the removal of i686 packages now than when (insert foundational package here - for example, CPython) stops supporting 32-bit architectures and we need to scramble to adapt.
Shouldn't Steam as a flatpak not just keep working?
This is just moving the problem from outside the Flatpak to inside the Flatpak: If we want to run all those old 32 butt games, they need 32 bit libraries somewhere.
Last edited by sudoer on 25 Jun 2025 at 9:47 am UTC

Upstream 32bit versions of applications/libraries started to be unsupported, untested and/or unused by upstream since some time now. "Doing nothing" and maintaining the status quo is worse than difficult: it's dangerous.
Fedora volunteers cannot keep providing a better product downstream than they have access to upstream. As a side note: can we please stop blabbering about corporate greed and for-profit progressism? These are guys helping for free in their free time. It's not IBM, it's not RedHat, it's a different thing. The corporate world abandoned 32bit AGES ago (and support it only in front of quite substantial payments).
Resources are scarce. Whoever is on the roof shouting that we must keep things running like twenty years ago should come down and start helping contributors. Or become one.
Associated projects, like RPMFusion, have the same resource starvation (people/time/interest) as Fedora maintainers, and they wouldn't pick up the slack. After all, it's rather unrealistic to offload one volunteer to overburden another.
Fedora is too small for Valve to care? Maybe. Or maybe this could be the last straw to push Gaben (always be praised His Name) to make Steam 64bit only and including in itself some "soft virtualization" in the form of 32bit runtime environments for abandonware 32bit native games. This wouldn't help extra-Steam native games. But at some point, we should stop complaining we can't run Amiga games without an emulator.
Other important subsystems, like Gamescope and OBS, are equally critical for a modern, gaming-friendly environment. We cannot dictate what others do with their free time, but asking kindly is always an option. And the best option is start contributing actively to the projects to help them get out of 32bit technical debt. That's the beauty of Open Source, after all: not backward compatibility, but technical excellence.
This need to happen, sooner or later. It's a matter of when, not if. It's too early now? Most likely yes. So, when it's the right time? Ubuntu tried it in 2019-2020 and it backfired horribly. But even five years ago, the rationale about letting 32bit die was strong and pressing. We're half a decade later debating exactly the same stuff, with exactly the same problems. https://canonical.com/blog/statement-on-32-bit-i386-packages-for-ubuntu-19-10-and-20-04-lts
Do I have a solution? Of course not. Will I miss some late 90's games unless there's an user-friendly way to run them? Probably. But in all honesty, I have no heart to ask Fedora maintainers (or any other distro maintaner, for that matter) to keep doing this maintenance work forever because Reeee mu games.
Last edited by syylk on 25 Jun 2025 at 10:51 am UTC
But at some point, we should stop complaining we can't run Amiga games without an emulator.Excuse me? I'll kill off every second daemon in my system if that'll let me run A500 games natively!

This is just moving the problem from outside the Flatpak to inside the Flatpak: If we want to run all those old 32 butt games, they need 32 bit libraries somewhere.
That's what the Steam Runntimes and org.freedesktop.Sdk.Compat.i386 are for. 32bit support on 64bit systems.
You do not need a single 32bit library to run 32bit software on 64bit systems with flatpak. Also there is WOW64 for Wine / Proton which is to run 32bit Windows game on 64bit. Even Windows uses 32bit abstractions on 64bit to run legacy software.
Removing 32bit support is not an issue at all.
i recomend this presentation for anyone thinking legacy dont matter, but i dont think its your case:It's not that legacy doesn't matter.
https://www.youtube.com/watch?v=65crLKNQR0E
It's that we do no longer really need legacy itself to keep other legacy alive.
Some things will no longer work, no doubt.
But I'd argue that those things were no longer important to people or someone would've made an effort to modernize or preseve them - just as people did with Flash, which can still be enjoyed without having to have Flash installed (with a bit of effort).
Who knows how many books we lost because nobody ever read them. It happens, it's normal.