Ubuntu 22.04 LTS – Common Problem 001 – Diagnosis and Fix

📖 ~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

Running apt or apt-get fails with lock errors such as /var/lib/dpkg/lock-frontend. Security updates and package installs are blocked until the lock is released.

Environment & Reproduction

Ubuntu 22.04 LTS servers or desktops where unattended-upgrades, snap refresh, or another apt process runs in parallel. Reproduce by opening two terminals and launching apt update concurrently.

Root Cause Analysis

dpkg permits a single writer to package databases. A second package tool sees active lock files; stale locks may remain after abrupt shutdowns.

Quick Triage

Check active package tasks first: ps aux | egrep ‘apt|dpkg|unattended’. If a process is active, wait for completion and re-run apt update.

Step-by-Step Diagnosis

Identify lock holders with sudo lsof /var/lib/dpkg/lock-frontend /var/cache/apt/archives/lock. Review apt history in /var/log/apt/history.log and journalctl -u unattended-upgrades.

Solution – Primary Fix

If no process owns the lock, remove stale lock files and repair package state: sudo rm -f /var/lib/dpkg/lock-frontend /var/cache/apt/archives/lock && sudo dpkg –configure -a && sudo apt -f install.

Solution – Alternative Approaches

Disable conflicting timers briefly: sudo systemctl stop apt-daily.timer apt-daily-upgrade.timer, run maintenance, then re-enable timers.

Verification & Acceptance Criteria

apt update and apt upgrade run without lock errors, dpkg –audit returns clean output, and unattended-upgrades resumes normally.

Rollback Plan

Restore timer state and package lists from backups if required. If package database corruption appears, recover from VM snapshot or filesystem backup.

Prevention & Hardening

Avoid concurrent package sessions, schedule maintenance windows, and keep unattended-upgrades enabled with predictable timing.

Related Errors & Cross-Refs

Could not get lock /var/lib/dpkg/lock-frontend, dpkg was interrupted, E: Sub-process /usr/bin/dpkg returned an error code.

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

View all Ubuntu 22.04 LTS tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Ubuntu Packaging Guide, man apt, man dpkg, Ubuntu unattended-upgrades documentation.