The dpkg was interrupted error looks scary, but it’s designed to protect your system. One command—sudo dpkg --configure -a—is usually all you need.
When in doubt, read the error message carefully. Often, Linux tells you exactly how to fix the problem.
Have you run into this error before? Let me know in the comments if the fix worked for you or if you hit another snag. The dpkg was interrupted error looks scary, but
Here’s a short article explaining the error and how to fix it.
sudo apt clean
sudo journalctl --vacuum-size=100M
sudo rm -rf /var/cache/apt/archives/*.deb.old # careful with rm
sudo mount -o remount,rw /
Or boot into recovery and run fsck if corruption is suspected. Have you run into this error before
If you’ve ever run apt install, apt upgrade, or apt-get and seen this error:
dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
It means a previous dpkg operation (like installing or configuring a package) was unexpectedly stopped or crashed. This leaves dpkg in an inconsistent state, and apt refuses to run until it’s fixed. sudo apt clean sudo journalctl --vacuum-size=100M sudo rm
While you now know how to fix the error, it's better to avoid it entirely. Here are best practices:
Author: A. System Administrator
Affiliation: Journal of Linux Systems Management
Date: April 21, 2026
sudo dpkg --audit
sudo dpkg --configure -a
sudo lsof /var/lib/dpkg/lock /var/lib/dpkg/lock-frontend /var/lib/apt/lists/lock /var/cache/apt/archives/lock
sudo tail -n 200 /var/log/dpkg.log
sudo journalctl -u apt -n 200 # if systemd logs apt
df -h
df -i
mount | grep 'on / '
sudo dmesg | tail -n 50
If the package database is more severely corrupted, run an audit and force a reconfigure of all packages:
sudo dpkg --audit
sudo dpkg --configure --pending
The --pending flag forces dpkg to configure only those packages that are marked as "unpacked but not configured."