Symptoms
- 'You have held broken packages' message
- Install fails with dependency errors
- 'dpkg was interrupted' warning
- Can't install or update anything
Likely causes
- CommonInterrupted install or updateClosing a terminal or losing power mid-install leaves the package database in a half-finished state.
- CommonConflicting third-party repositoryAn added PPA or repo can require different versions of shared libraries.
- PossibleMixing package managers or manual .deb/.rpm installsInstalling packages outside the normal system can create version conflicts.
- PossibleOutdated package indexThe local list of available packages is stale and doesn't match the repository anymore.
What to do
- On Debian/Ubuntu, run 'sudo apt update' first to refresh the package index.
- Run 'sudo apt --fix-broken install' to let apt try to resolve and repair dependencies automatically.
- If dpkg was interrupted, run 'sudo dpkg --configure -a' to finish any half-installed packages.
- On Fedora/RHEL, run 'sudo dnf clean all' followed by 'sudo dnf distro-sync' to resolve conflicts.
- If a specific recently added repository is the cause, disable or remove it (delete its file from /etc/apt/sources.list.d/ or use 'sudo add-apt-repository --remove').
- Retry the original install or update once the fix commands complete without errors.
- As a last resort, note down key installed packages and consider a fresh OS reinstall if the system stays inconsistent.
Tools and parts
- Terminal access with sudo privileges
When to call a pro
If fix-broken commands loop without resolving, a Linux support forum or professional can review your exact package list.
Safety
Generally low risk
Generally low risk for a careful person. Stop if anything looks different from what this guide describes.