How to fix E: Unmet dependencies. Try 'apt --fix-broken install' with no packages in APT

APTINTERMEDIATEHIGHUpdated Dec 29, 2025· 245 views

When apt package manager encounters broken dependencies, it prompts you to run 'apt --fix-broken install'. This error indicates that your package dependency chain is broken and needs repair before you can install or upgrade packages.

Quick fix

Fixes E: Unmet dependencies. Try 'apt --fix-broken install' with no packages

sudo apt-get update
sudo apt --fix-broken install
  1. Update package lists and attempt automatic dependency fix
  2. Check for held packages preventing dependency resolution
  3. Use apt-get with problem resolver debug to see detailed dependency info
  4. Use aptitude for more intelligent dependency resolution
apt — error
sudo apt-get update
sudo apt --fix-broken install
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages

What this error means

Unmet dependencies occur when the apt package manager detects that one or more packages require other packages that are either missing, incompatible, or not installed. This typically happens during package installations, upgrades, or removals when a package's required dependencies cannot be satisfied. The package manager intentionally blocks the operation to prevent system instability. The error suggests running 'apt --fix-broken install' to automatically resolve dependency issues by downloading and installing the required packages. However, this command sometimes fails if the dependency conflict is too complex or if problematic packages need to be removed.

Typical symptoms

  • apt, apt-get, or other package managers fail with 'Unmet dependencies' message
  • System package updates fail midway through installation
  • Third-party repository packages create dependency conflicts
  • Held packages (packages marked to not be upgraded) prevent dependency resolution
  • Installation fails even after running 'apt --fix-broken install'

Common causes

  1. Partial or interrupted package installation leaving broken dependencies
  2. Third-party APT repositories with incompatible package versions
  3. Packages held at specific versions that don't satisfy other packages' requirements
  4. Conflicting packages from multiple repositories trying to install simultaneously
  5. Manually installed packages without proper dependency checks

How to fix "E: Unmet dependencies. Try 'apt --fix-broken install' with no packages"

1Update package lists and attempt automatic dependency fix

First, update your package cache and try the automatic fix suggested by apt:

bash
sudo apt-get update
sudo apt --fix-broken install

This command tells apt to download and install any missing dependencies. If this succeeds, your issue is resolved.

2Check for held packages preventing dependency resolution

If the above fails, check if any packages are held (prevented from being upgraded/removed):

bash
apt-mark showhold

If packages are held, they may prevent dependency resolution. You can unhold them with:

bash
sudo apt-mark unhold package-name
sudo apt --fix-broken install

Replace package-name with the actual package name shown in the hold list.

3Use apt-get with problem resolver debug to see detailed dependency info

For more detailed information about what's causing the dependency conflict:

bash
sudo apt-get -o Debug::pkgProblemResolver=yes dist-upgrade

The verbose output will show which packages are conflicting and why. This helps you understand what's happening so you can make informed decisions about which packages to remove or downgrade.

4Use aptitude for more intelligent dependency resolution

The aptitude package manager is often better at resolving complex dependency conflicts than apt-get:

bash
sudo apt-get install aptitude
sudo aptitude install -f

Aptitude uses more sophisticated algorithms to find solutions and may succeed where apt-get fails. It may suggest removing or downgrading conflicting packages.

5Identify and remove problematic packages as last resort

If previous steps fail, you may need to remove the packages causing the conflict. First, use apt to show which packages are broken:

bash
sudo apt-get check

Once you identify the problematic package, try a dry run first:

bash
sudo apt-get remove --dry-run package-name

If the dry run looks safe, remove it:

bash
sudo apt-get remove package-name
sudo apt --fix-broken install

Then you can reinstall the package or find a compatible alternative version.

6Install specific package versions if needed

If a package is causing conflicts, you can explicitly install a compatible version:

bash
sudo apt-get install package-name=version-number

First, see available versions:

bash
apt-cache policy package-name

This shows all available versions in your repositories. Choose a compatible one and install it explicitly.

Advanced notes

For persistent issues, investigate your APT sources. Third-party PPAs (Personal Package Archives) are a common culprit. List your sources with 'software-properties-gtk' or by checking '/etc/apt/sources.list' and '/etc/apt/sources.list.d/'. Disabling problematic repositories often resolves unmet dependencies. If you're using containers or cloud instances, ensure your base image's package repositories are compatible with any third-party packages you're adding. Some distributions (Ubuntu, Debian, Linux Mint) have slightly different repository configurations that can cause conflicts if mixed.

Frequently asked questions

What does "E: Unmet dependencies. Try 'apt --fix-broken install' with no packages" mean?
Unmet dependencies occur when the apt package manager detects that one or more packages require other packages that are either missing, incompatible, or not installed. This typically happens during package installations, upgrades, or removals when a package's required dependencies cannot be satisfied. The package manager intentionally blocks the operation to prevent system instability.
How do I fix "E: Unmet dependencies. Try 'apt --fix-broken install' with no packages"?
When apt package manager encounters broken dependencies, it prompts you to run 'apt --fix-broken install'. This error indicates that your package dependency chain is broken and needs repair before you can install or upgrade packages.
What causes "E: Unmet dependencies. Try 'apt --fix-broken install' with no packages"?
Partial or interrupted package installation leaving broken dependencies Third-party APT repositories with incompatible package versions Packages held at specific versions that don't satisfy other packages' requirements
Is the "E: Unmet dependencies. Try 'apt --fix-broken install' with no packages" error serious?
Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Official resources & further reading