Package Management (Apt/Dnf/Pacman Internals)

Unsticking dpkg when the pre-install script loses its mind

🧩 The Challenge

You know that heart-stopping moment when a package update hangs indefinitely because a post-install script is stuck waiting for a service that never restarts? You try to kill it, but then dpkg locks the database and everything else fails.

💡 The Fix

Dive into the status files directly to purge the offending package’s triggers and post-install flags manually. It’s a bit surgical, but it beats reinstalling the whole OS.

sed -i '/^Package: <package_name>/,/^$/d' /var/lib/dpkg/status
rm /var/lib/dpkg/info/<package_name>.*
dpkg --configure -a

⚙️ Why It Works

Dpkg keeps its “world state” in that status file, and if you can just excise the entry for the broken package, the database effectively forgets it was ever there. Removing the corresponding script files in /var/lib/dpkg/info ensures that dpkg doesn’t try to run that same failing logic again once you re-run the configuration.

🚀 Pro-Tip: Always keep a backup of that status file before editing it with sed, because one wrong regex and you are officially having a very bad day.

Linux Tips & Tricks | © ngelinux.com | 9/16/2026