How to Fix ‘Unmet Dependencies’ Errors When Installing Steam on Ubuntu

You try to install Steam on Ubuntu, and instead of a game library you get a wall of red text about unmet dependencies and packages that will not be installed. It looks serious, but in most cases your system is not broken. One missing 32-bit library, a held package, or the wrong Steam installer is usually all that stands in your way.

Steam needs a set of 32-bit libraries even on a 64-bit system, because many games and parts of the Steam client itself are still 32-bit. When Ubuntu cannot enable or fetch those libraries, the installer reports unmet dependencies. This guide shows you how to fix the causes in the right order.

Quick Answer

Update your system fully, enable the 32-bit architecture with sudo dpkg --add-architecture i386, run sudo apt update, and then install Steam with sudo apt install steam-installer. If APT still reports held or broken packages, run sudo apt install -f and sudo apt --fix-broken install before trying again. Avoid mixing the website .deb with the repository version.

Why Steam Triggers Unmet Dependencies

An unmet dependencies error means APT found a package Steam needs, but cannot install an acceptable version of it. That can happen for several different reasons, and each needs a slightly different fix:

• The 32-bit architecture is not enabled, so i386 libraries simply do not exist as far as APT is concerned.
• The multiverse repository, where Steam lives, is turned off.
• Your package lists are out of date, so APT is working from old information.
• A previous failed install left packages in a broken or half-configured state.
• Held packages are frozen at old versions that conflict with what Steam needs.
• You downloaded Steam’s installer .deb from the web, and it conflicts with the repository version.

The error message names the specific packages involved. Reading those names carefully turns a scary wall of text into a short shopping list of what to repair.

Step 1: Update Everything First

Never install a complex package onto a half-updated system. Bring everything current before touching Steam.

1. Open a terminal with Ctrl + Alt + T.
2. Refresh package lists: sudo apt update
3. Install all pending updates: sudo apt full-upgrade
4. Finish any interrupted setup: sudo dpkg --configure -a
5. Reboot if the update installed a new kernel or major libraries.

Many dependency errors quietly disappear after this step alone, because the conflicting package was simply an old version that an update replaces. For a fuller explanation of these commands, see our guide on how to update Ubuntu correctly from the terminal.

Step 2: Enable 32-Bit Support and the Multiverse Repository

This is the heart of the fix for most users. Steam’s required libraries are 32-bit, and Steam itself is distributed through the multiverse component.

1. Enable the 32-bit architecture: sudo dpkg --add-architecture i386
2. Enable the multiverse repository: sudo add-apt-repository multiverse
3. If the command asks about enabling restricted and universe components too, you can accept them; they provide other commonly needed libraries and drivers.
4. Refresh package lists so APT can see the new architecture and repository: sudo apt update
5. Watch the output. You should see download lines mentioning i386 packages. That confirms 32-bit support is active.

Without that refresh, APT still does not know the 32-bit packages exist, and the Steam install will fail with exactly the same unmet dependencies message as before.

Step 3: Install Steam the Repository Way

With the groundwork done, install Steam from Ubuntu’s repositories rather than from a downloaded file.

1. Install the launcher package: sudo apt install steam-installer
2. Read the list of additional packages APT proposes. It will include many :i386 libraries. That is normal and expected.
3. Confirm the installation and let it complete.
4. Launch Steam from the app grid. The first launch downloads the full client, which can take several minutes.
5. Sign in and let the client update itself before judging performance.

The official Steam support page for Linux installation also recommends the distribution package route and explains the first-launch client download. If APT still refuses at this point, note the exact package names it complains about and continue to the repair steps below.

Step 4: Repair Broken and Held Packages

If earlier failed attempts left your package system in a bad state, repair it before retrying Steam.

Fix Broken Installs

1. Ask APT to repair dependencies: sudo apt install -f
2. Run the dedicated repair form as well: sudo apt --fix-broken install
3. Complete any pending configuration: sudo dpkg --configure -a
4. Try the Steam install again: sudo apt install steam-installer

Check for Held Packages

Held packages are frozen on purpose or by accident, and a frozen library can block everything behind it.

1. List held packages: apt-mark showhold
2. If a library Steam needs is held, release it: sudo apt-mark unhold packagename
3. Update and upgrade again: sudo apt update && sudo apt full-upgrade
4. Retry the Steam installation.

Only unhold packages you recognise or that the error message names. If a package was held deliberately by an administrator on a shared machine, ask before changing it.

Step 5: If You Used the Downloaded .deb, Clean Up First

Valve’s website offers a steam.deb file, and installing it alongside repository packages is a frequent source of exactly this error. If that is your situation, remove the mixture and start clean.

1. Remove the downloaded installer version: sudo apt remove steam-launcher steam — ignore messages about packages that are not installed.
2. Repair anything left behind: sudo apt install -f
3. Make sure 32-bit support and multiverse are enabled, as in Step 2.
4. Install the repository version: sudo apt install steam-installer

Choosing one installation source and sticking to it prevents the two packaging styles from fighting over the same libraries in the future.

Step 6: Install a Named Missing Library Directly

Occasionally the error points to one specific library, often a graphics-related 32-bit package. Installing it explicitly can unblock the whole chain.

1. Read the error and identify the named package, for example a library ending in :i386.
2. Install it directly: sudo apt install packagename:i386, using the real name from your error.
3. If APT proposes removing many packages to do this, stop. That is a warning sign of a deeper conflict; return to Step 4 instead of accepting.
4. Once the library installs cleanly, run sudo apt install steam-installer again.

Graphics drivers deserve special attention here. If the named packages relate to NVIDIA or AMD drivers, install the correct driver from Software & Updates under Additional Drivers first, reboot, and then install Steam. Mixing driver versions between 64-bit and 32-bit is a classic hidden cause of this error.

Common Mistakes and Useful Tips

• Skipping the i386 step: This is the number one cause. Steam cannot install without 32-bit libraries, no matter how many times you retry the same command.
• Accepting a mass removal: If APT says it will remove your desktop or dozens of core packages to install Steam, cancel. That proposal means a serious repository conflict, not a normal install.
• Mixing installer sources: Pick the repository package or Valve’s file, never both. The repository route is easier to repair and updates with your system.
• Adding random PPAs for libraries: Steam needs only standard Ubuntu repositories plus multiverse. Extra PPAs often create the very version conflicts behind this error.
• Tip — read the first named package: Dependency chains are long, but the fix usually starts with the first package APT says it cannot install. Focus there.
• Tip — consider the Snap or Flatpak as a fallback: If a heavily customised system refuses all repairs, Steam as a snap is an alternative, though the repository version remains the best-supported choice on Ubuntu. Valve’s official Steam download page lists the supported options.

Conclusion

Unmet dependencies when installing Steam almost always trace back to missing 32-bit support, a disabled multiverse repository, stale package lists, or damage from an earlier failed install. Update fully, enable the i386 architecture, refresh your lists, repair broken or held packages, and install steam-installer from the repositories. Work through the steps in order and read the package names APT gives you, and Steam should install and launch without the dependency wall standing in your way.

Frequently Asked Questions

Why does Steam need 32-bit libraries on a 64-bit system?

The Steam client and many games were built as 32-bit programs. Ubuntu can run them on a 64-bit system, but only if the matching 32-bit libraries are available, which is why enabling the i386 architecture is essential.

Is it safe to enable the multiverse repository?

Yes. Multiverse is an official Ubuntu component containing software with licensing restrictions, including Steam and some drivers. It is maintained through Ubuntu’s normal channels and is required for a standard Steam install.

APT wants to remove many packages to install Steam. Should I accept?

No. A normal Steam install adds packages; it does not remove your desktop or core system. Cancel, repair broken packages with sudo apt install -f, check for conflicting PPAs or held packages, and try again.

Should I download Steam from the website or install it from Ubuntu?

On Ubuntu, the repository package steam-installer is the smoother choice because APT resolves all 32-bit dependencies automatically. The website file works too, but mixing the two is a common cause of dependency errors.

Steam installed but will not launch. Is that the same problem?

Not usually. A launch failure after a successful install is often a graphics driver or runtime issue. Update your system, install the recommended driver from Additional Drivers, reboot, and launch Steam from a terminal to read any error it prints.