Running apt commands simultaneously (e.g., opening two terminal windows and running sudo apt install in both) will cause a lock conflict. While this usually triggers a different lock error, it can escalate into a "was interrupted" state if the conflict crashes the process.
Immediately after running sudo dpkg --configure -a , Dpkg may trigger post-installation scripts that rebuild caches (e.g., ldconfig , initramfs ). This can consume CPU for 1–2 minutes. Reboot after the process finishes to clear temporary slowdowns. Dpkg Was Interrupted You Must Manually Run Sudo Dpkg
By running sudo dpkg --configure -a followed by sudo apt --fix-broken install , you can recover your system in under 60 seconds. Bookmark this guide, and next time you see that red text, you will know exactly how to reclaim control of your Linux machine. Running apt commands simultaneously (e
Once you run this, your system will resume the installation process from exactly where it was cut off. 🏗️ Step-by-Step Recovery Guide This can consume CPU for 1–2 minutes
In extremely rare cases, even after sudo dpkg --configure -a , the system reports that the package database is corrupted beyond repair. You see errors like: “dpkg: unrecoverable fatal error, aborting: files list file for package 'xyz' is missing.”