dpkg Was Interrupted, Run dpkg –configure -a

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Package commands abort because dpkg is left in an incomplete state.

Environment & Reproduction

Ubuntu 16.04 systems after interrupted upgrades or abrupt reboots.

Root Cause Analysis

A package configure step did not complete, leaving pending maintainer scripts.

Quick Triage

Confirm interrupted state and identify packages awaiting configuration.

Step-by-Step Diagnosis

Inspect dpkg status records, logs, and failing package script output.

Solution – Primary Fix

Run dpkg –configure -a, then repair dependencies and rerun apt operations.

Solution – Alternative Approaches

Purge broken packages and reinstall from known-good repositories.

Verification & Acceptance Criteria

dpkg reports no pending actions and apt operations finish successfully.

Rollback Plan

Restore package database backups if remediation worsens dependency conflicts.

Prevention & Hardening

Avoid power interruption during upgrades and use controlled maintenance windows.

Related Errors & Cross-Refs

Sub-process /usr/bin/dpkg returned an error code and unmet dependency errors.

Related tutorial: View the step-by-step tutorial for Ubuntu 16.04 LTS.

View all Ubuntu 16.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Ubuntu package recovery documentation for interrupted dpkg workflows.