Enable 32-bit libraries for gaming
You launch a native Linux game or a wrapper script, and the window vanishes instantly. The terminal prints error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory. You are running Fedora Workstation. The system is 64-bit. The game requires 32-bit libraries. Fedora disables 32-bit package support by default to reduce disk usage and attack surface. You need to enable the i686 architecture in the package manager and install the compatibility libraries.
Identify the binary architecture
Before installing libraries, confirm the game actually needs 32-bit support. Some games are 64-bit only. Some are universal. Use the file command to inspect the binary.
Here is how to check the architecture of a game executable.
file /path/to/game_binary
# WHY: Reads the ELF header and reports the architecture.
# Output "ELF 32-bit LSB executable" means you need i686 libraries.
# Output "ELF 64-bit LSB executable" means the game runs on 64-bit only.
If the output says ELF 32-bit, proceed with the installation. If it says ELF 64-bit, the missing library error comes from a different cause. Check the game documentation or forum threads.
Run file on the binary first. Guessing the architecture wastes time and disk space.
Why Fedora hides 32-bit packages
Fedora ships only 64-bit packages. This is a deliberate choice. 64-bit code uses larger address spaces, supports more CPU registers, and benefits from modern security features like KASLR and shadow stacks. Shipping 32-bit packages by default would double the repository size and increase the maintenance burden.
The kernel supports 32-bit binaries. The hardware supports 32-bit binaries. The gap is the userspace libraries. When you enable the i686 architecture, dnf learns to look for 32-bit versions of packages. Enabling the architecture does not install anything. It only makes the packages available. You retain full control over what gets installed.
Think of the package manager as a warehouse. By default, the 32-bit aisle is locked. You are holding the key. Unlocking the aisle lets you walk in and grab what you need. It does not force you to buy everything on the shelf.
Enable the architecture before you install. dnf will silently ignore missing architectures if you skip this step.
Enable the i686 architecture
Use dnf config-manager to enable the 32-bit architecture across all repositories. This command modifies the configuration files in /etc/yum.repos.d/. Editing files in /etc/ is safe and persists across updates. Never edit files in /usr/lib/. Those files are owned by packages and will be overwritten.
Here is how to enable the architecture globally.
sudo dnf config-manager --set-enabled i686
# WHY: Updates all repo files to include the [i686] section.
# This tells dnf to query repositories for i686 packages.
# The change is persistent and survives repository updates.
Run dnf upgrade --refresh after changing repository configurations. This forces dnf to download fresh metadata and recognize the new architecture. Skipping the refresh can cause dnf to cache stale metadata and refuse to find 32-bit packages.
Refresh the metadata. A stale cache is the most common reason packages appear missing after enabling an architecture.
Install the core compatibility libraries
Most games depend on the C and C++ standard libraries. The glibc package provides the core system calls. The libstdc++ package provides the C++ runtime. The libgcc package provides low-level compiler support. Install the 32-bit versions of these packages.
glibc is the GNU C Library. It provides the interface between applications and the kernel. Functions like open, read, write, and malloc come from glibc. The 32-bit version lives in /lib/libc.so.6. The 64-bit version lives in /lib64/libc.so.6. Both can coexist. The dynamic linker selects the correct version based on the binary architecture.
libstdc++ implements the C++ standard library. It provides classes like std::string and std::vector. Games compiled with GCC or Clang link against this library. The version string in the error message, like GLIBCXX_3.4.30, indicates the minimum version required. Ensure your system package meets this requirement.
Here is the command to install the essential 32-bit libraries.
sudo dnf install glibc.i686 libstdc++.i686 libgcc.i686
# WHY: Installs the runtime libraries required by 32-bit binaries.
# glibc.i686 provides basic functions like malloc and printf.
# libstdc++.i686 is required by almost all compiled C++ games.
# libgcc.i686 handles exception handling and floating-point operations.
If the game uses specific multimedia frameworks, you may need additional packages. Install libX11.i686 for X11 windowing support. Install libpulse.i686 for PulseAudio sound. Install alsa-lib.i686 for direct ALSA access.
Install the libraries. The game will not launch until the shared objects are present in the library paths.
Add RPM Fusion for gaming dependencies
Fedora cannot ship proprietary codecs or certain graphics drivers. Many games require these components. RPM Fusion provides the non-free packages that Fedora excludes. If you are setting up a gaming system, you likely need RPM Fusion.
Here is how to enable RPM Fusion and install the free and non-free repositories.
sudo dnf install -y https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm
# WHY: Downloads and installs the RPM Fusion release packages.
# The free repo contains open-source drivers and codecs.
# The nonfree repo contains proprietary firmware and codecs.
# This command uses rpm -E to insert the correct Fedora release number.
After installing RPM Fusion, run dnf upgrade --refresh again. The new repositories need to be indexed.
Enable RPM Fusion. Gaming on Fedora almost always requires the non-free repository for Vulkan drivers and multimedia support.
Steam and Proton runtime
Steam includes its own runtime environment. Proton, the compatibility layer for Windows games, ships with its own 32-bit libraries. Steam often works without system 32-bit libraries.
Native Linux games do not include a runtime. They rely entirely on the system libraries. If you play native games, you must install glibc.i686 and libstdc++.i686.
Some native games use Steam's runtime as a fallback. This behavior is not guaranteed. Relying on the system libraries ensures consistent behavior across all launchers.
Check the launcher documentation. Steam handles its own dependencies. Native games depend on the system.
Verify the installation
Confirm that the 32-bit libraries are installed. Check the package list for i686 entries. Verify that a binary can link against the libraries.
Here is how to list installed 32-bit packages.
rpm -qa --qf '%{NAME}-%{ARCH}\n' | grep i686 | head -10
# WHY: Queries the rpm database for packages with i686 architecture.
# The output lists package names and their architecture.
# Look for glibc.i686 and libstdc++.i686 in the results.
Test a specific game binary. Use ldd to check for missing dependencies.
ldd /path/to/game_binary | grep "not found"
# WHY: Lists shared library dependencies and highlights missing ones.
# If the output is empty, all libraries are resolved.
# If lines appear, install the missing library packages.
Run ldd on the binary. The error message tells you exactly which package is missing.
Common errors and fixes
You may encounter errors during installation or runtime. Identify the error string and apply the fix.
If dnf prints Error: Nothing provides glibc.i686 needed by..., the architecture is not enabled. Run sudo dnf config-manager --set-enabled i686 and refresh the metadata.
If you see error while loading shared libraries: libstdc++.so.6: version 'GLIBCXX_3.4.30' not found, the installed libstdc++ is too old. Run sudo dnf upgrade libstdc++.i686 to get the latest version.
Enabling i686 introduces the risk of multiarch conflicts. This happens when two packages provide the same file but with different architectures. Fedora's package manager handles this well, but third-party repositories can cause issues.
If dnf aborts with Transaction test error: package foo-1.0.x86_64 conflicts with foo-1.0.i686, a conflict exists. Check the repository sources. Disable the offending repository temporarily. Run dnf clean all. Retry the installation.
Use dnf repoquery --whatprovides /path/to/file to find which package owns a conflicting file.
Run dnf history to review recent transactions. If a conflict appears after an update, use dnf history undo to revert the change. The history log provides a safe rollback path.
Read the error before guessing. The log line contains the solution.
Reverting 32-bit support
If you no longer need 32-bit libraries, you can remove them and disable the architecture. This frees disk space and reduces the update payload.
Here is how to remove the 32-bit packages.
sudo dnf remove glibc.i686 libstdc++.i686 libgcc.i686
# WHY: Removes the 32-bit packages and their dependencies.
# dnf calculates the removal order to avoid breaking 64-bit packages.
# This command may remove other 32-bit packages installed as dependencies.
Disable the architecture to prevent accidental reinstallation.
sudo dnf config-manager --set-disabled i686
# WHY: Removes the [i686] section from repository files.
# dnf will no longer query for 32-bit packages.
# This change persists across updates.
Remove the packages before disabling the architecture. dnf needs the architecture enabled to calculate the removal transaction.
Decision matrix
Use dnf config-manager --set-enabled i686 when you need persistent 32-bit support for multiple games and applications.
Use dnf install --setopt=arch=i686 package when you need a single 32-bit package without enabling the architecture globally.
Use RPM Fusion when you need proprietary codecs, Vulkan drivers, or firmware that Fedora cannot ship.
Stay on 64-bit only when you are running a server or a minimal container where 32-bit games will never execute.
Choose the scope that matches your workload. Enabling the architecture is the standard approach for a gaming desktop.