You are mid-upgrade, it is 2 AM, and apt is stuck on a post-installation script that refuses to die. It happens to everyone eventually. Usually, you just kill the process and hope for the best, but that is how you end up with a broken state that apt refuses to touch for the rest of the night. If you have been there, you know that manual intervention in /var/lib/dpkg/info is often the only way out.

When apt locks you out of the machine

When a maintainer script hangs, it is often due to some systemd service interaction or a stray daemon failing to signal completion. Trying to force apt to proceed via flags usually does nothing because the lock is already held by the hanging process. You have to locate the offending script and inspect why it is waiting on something that clearly is not coming.

grep -l 'packagename' /var/lib/dpkg/info/*.postinst

• Check /var/lib/dpkg/status for the package state
• Move the offending postinst script to a temp location to break the cycle
• Run dpkg –configure -a to force the state machine to reconcile
• Audit the log in /var/log/apt/term.log to find exactly where it hung

After you move the script and fix the configuration, do not just walk away. The package is now missing its post-install steps, which usually involve creating system users or setting binary permissions. Reinstalling the package with the –reinstall flag is mandatory if you want to ensure the filesystem is actually consistent with what the packaging system expects. It is annoying, but it beats finding out your service won’t start because the post-install script never finished setting up its runtime directory.