32-bit Gaming Support#

Bluefin's image-based design means /usr is read-only — you can't dnf install host-level multilib packages at runtime. 32-bit gaming compatibility is handled by two purpose-built mechanisms instead:

Host-level multilib is intentionally absent. Both paths provide GPU-accelerated 32-bit gaming without touching the base image 1.

Flatpak i386 Platform Extensions#

Steam Flatpak gets its 32-bit graphics support via org.freedesktop.Platform.GL32.* extensions — the Flatpak runtime equivalent of host multilib GPU drivers. These are installed automatically alongside Steam, but mismatches can cause errors at launch.

NVIDIA: Driver Version Mismatch#

The most common issue is an NVIDIA driver version mismatch. Steam will display 2:

The following i386 compatibility flatpak extensions are not installed, Steam may not work properly:
org.freedesktop.Platform.GL32.nvidia-595-71-05

Try running flatpak update; if it doesn't help, install the extensions manually:
flatpak install org.freedesktop.Platform.GL32.nvidia-595-71-05//25.08

The extension name encodes the host driver version. When the Flatpak extension registry doesn't yet have a matching GL32 extension for your installed NVIDIA driver, Steam flags it as missing. The fix 2:

1. Run flatpak update — this resolves it in most cases once the extension is published
2. If not resolved, install the specific extension manually:
   ⧉

   flatpak install org.freedesktop.Platform.GL32.nvidia-<your-driver-version>//<runtime-version>
   

Tip: The extension version (//25.08 etc.) must match the Flatpak runtime your Steam installation is using. Check with flatpak info com.valvesoftware.Steam.

Missing 32-bit Libraries at First Launch#

Some users see a warning at first Steam launch about missing libgtk-x11-2.0.so.0 and libbz2.so.1.0 3. This was resolved in recent builds — if you're on a current image, it should not occur.

Steambox Container: Native lib32 Stack#

The steambox container is an Arch Linux-based Distrobox image that ships a complete 32-bit gaming stack — no Flatpak GL32 extensions needed. All lib32 packages are built into the image at container build time.

Images:

• ghcr.io/ublue-os/steambox:latest — KDE portals
• ghcr.io/ublue-os/steambox-gnome:latest — GNOME portals (recommended for Bluefin)

32-bit packages included#

From official Arch repos 4:

From AUR 5:

Steam is installed natively inside the container (not as a Flatpak), using the container's own multilib environment — no GL32 extension dependency. The container also sets makepkg.conf to use -march=native -mtune=native for packages compiled inside it 6.

Setup#

# Create the container (GNOME variant for Bluefin)
distrobox create --image ghcr.io/ublue-os/steambox-gnome:latest --name gaming

# Enter and launch
distrobox enter gaming
steam &

For a persistent, auto-starting container managed by systemd, see the Quadlet setup in the Gaming guide.

Choosing the Right Approach#

When to use Bazzite instead#

If you need fsync kernel patches (heavy Proton/Wine workloads) or the Xbox wireless controller driver (xone, removed from Bluefin on 2026-02-17), rebase to Bazzite:

sudo bootc switch ghcr.io/ublue-os/bazzite:latest

Bluefin ships a stock kernel without gaming-specific scheduler modifications .

Key references#

• Steambox Containerfile — full package list
• Gaming docs — ujust install-gaming-flatpaks and Quadlet setup
• i386 extension mismatch issue — known NVIDIA GL32 issue and resolution
• First-launch 32-bit library warning — resolved in current builds