Linux APT 'Unmet Dependencies — Broken Packages' Error

APT 'unmet dependencies' or 'broken packages' error means package dependency requirements cannot be satisfied, blocking installation. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: Dependency resolution failure prevents package installation. Can cascade — one broken package can block many others. Mixing repositories (PPAs) is the most common cause. apt-get -f install attempts to fix broken dependencies automatically. In severe cases, dpkg --force may be needed (use cautiously). Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Third-party PPA providing packages incompatible with system versions. Partial upgrade leaving packages in inconsistent state. Manually installing .deb files that conflict with repository versions. Repository metadata out of date. Forced package removal breaking dependency chains. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Try automatic fix: sudo apt --fix-broken install. Update package lists: sudo apt update. Remove problematic PPA: sudo add-apt-repository --remove ppa:name/ppa. Force reconfigure: sudo dpkg --configure -a. As last resort, identify and remove the conflicting package: sudo dpkg -r --force-depends package-name then sudo apt --fix-broken install. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our Linux Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.