You Must Manually Run Sudo Dpkg Configure To Correct The Problem !exclusive! — Dpkg Was Interrupted

sudo apt-get download dpkg sudo dpkg -i --force-all dpkg_*.deb

The error message appeared immediately. The lock file existed at /var/lib/dpkg/lock (removed automatically by dpkg --configure -a ). The hello package was in half-configured state as per /var/lib/dpkg/status . sudo apt-get download dpkg sudo dpkg -i --force-all dpkg_*

The --pending flag forces dpkg to configure only those packages that are marked as "unpacked but not configured." The --pending flag forces dpkg to configure only

Once upon a time in the land of Linux, a user named decided it was finally time to update his system. He opened the terminal, typed his commands with confidence, and watched as the text scrolled by like digital rain. You might see additional errors like Cannot write

Sometimes, sudo dpkg --configure -a itself fails. You might see additional errors like Cannot write to lock file or Sub-process /usr/bin/dpkg returned an error code . When that happens, use the following advanced fixes.