If you’re on a laptop, ensure you’re plugged into power before starting a large dist-upgrade .
When this happens, dpkg leaves a lock file ( /var/lib/dpkg/lock ) and an internal flag indicating an incomplete operation. More importantly, one or more packages remain in a half-configured or triggers-pending state.
The error is common but rarely serious. In most cases, the solution is exactly what the message says: open a terminal and type that command. However, when the standard fix fails, you now have a toolkit of advanced methods – from removing lock files to rebuilding the dpkg status database.
Never close the window while a process is running. If you’re on a laptop, ensure you’re plugged
If a specific software package is causing the loop and refusing to configure, you can force remove that single package to unstick the system.
sudo cp /var/lib/dpkg/status /var/lib/dpkg/status.bak
I can provide a tailored solution once I know these details. Share public link The error is common but rarely serious
sudo dpkg --configure -a sudo apt-get install -f
Fixing the "dpkg was interrupted" Error in Linux If you’ve been managing a Debian-based system like Ubuntu, Linux Mint, or Kali, you’ve likely encountered this daunting terminal message:
Fix: "dpkg was interrupted, you must manually run..." Error in Linux Never close the window while a process is running
sudo apt update sudo apt install nodejs
sudo dpkg --configure -a