Fixing apt-get Lock Errors (Could Not Get Lock)

The "Could not get lock" error is one of the most common issues on Ubuntu/Debian systems. It happens when another process is using apt or dpkg. This guide covers safe resolution without corrupting your package manager.

Environment

OS: Ubuntu 22.04 LTS
Package manager: apt 2.4.8

$ apt --version
apt 2.4.8 (amd64)

The Problem

$ sudo apt update
E: Could not get lock /var/lib/dpkg/lock-frontend (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (11: Resource temporarily unavailable), are you root?

# Or this variant
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/

Analysis

Step 1: Identify the Lock Holder

# Find process holding the lock
$ sudo lsof /var/lib/dpkg/lock-frontend
COMMAND    PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
dpkg       1234 root    5uW  REG  253,1        0 123456 /var/lib/dpkg/lock-frontend

# Or check with fuser
$ sudo fuser /var/lib/dpkg/lock-frontend
/var/lib/dpkg/lock-frontend:  1234

# Check what process is running
$ ps aux | grep 1234
root      1234  0.0  0.1  24576 13432 pts/0    S+   10:00   0:00 dpkg --configure -a

Step 2: Check for Unattended Upgrades

# Check if unattended-upgrades is running
$ sudo systemctl status unattended-upgrades
● unattended-upgrades.service - Unattended Upgrades Download and Apply
     Active: active (running) since Sat 2025-05-22 09:55:00 WET; 5min ago

# Check apt history
$ sudo tail -20 /var/log/apt/history.log
Start-Date: 2025-05-22  09:55:00
Commandline: /usr/bin/unattended-upgrade
...

Step 3: Check for Stale Locks

# Check lock file ages
$ ls -la /var/lib/dpkg/lock*
-rw-r----- 1 root root    0 May 22 08:00 /var/lib/dpkg/lock
-rw-r----- 1 root root    0 May 22 08:00 /var/lib/dpkg/lock-frontend
-rw-r----- 1 root root    0 May 22 08:00 /var/lib/dpkg/lock-io

$ ls -la /var/lib/apt/lists/lock*
-rw-r----- 1 root root    0 May 22 08:00 /var/lib/apt/lists/lock

Solution

Fix 1: Wait for Process to Complete

# Check if process is still active
$ sudo ps aux | grep -E "dpkg|apt" | grep -v grep
root      1234  0.0  0.1  24576 13432 pts/0    S+   10:00   0:00 dpkg --configure -a

# If it's actively working, wait
$ sudo tail -f /var/log/dpkg.log
# Watch for progress

# Wait and retry
$ sleep 30
$ sudo apt update

Fix 2: Kill the Process

# If process is stuck
$ sudo kill 1234

# Wait for process to terminate
$ sleep 5

# Verify lock is released
$ sudo fuser /var/lib/dpkg/lock-frontend
# Should return nothing

# Retry
$ sudo apt update

Fix 3: Force Remove Stale Locks

# DANGER: Only if no apt/dpkg process is running
$ sudo fuser -k /var/lib/dpkg/lock-frontend
$ sudo fuser -k /var/lib/dpkg/lock
$ sudo fuser -k /var/lib/apt/lists/lock

# Remove lock files (last resort)
$ sudo rm /var/lib/dpkg/lock-frontend
$ sudo rm /var/lib/dpkg/lock
$ sudo rm /var/lib/apt/lists/lock

# Reconfigure dpkg
$ sudo dpkg --configure -a

# Retry
$ sudo apt update

Fix 4: Disable Unattended Upgrades Temporarily

# Stop unattended-upgrades
$ sudo systemctl stop unattended-upgrades
$ sudo systemctl disable unattended-upgrades

# Do your apt operations
$ sudo apt update
$ sudo apt upgrade

# Re-enable if desired
$ sudo systemctl enable unattended-upgrades
$ sudo systemctl start unattended-upgrades

Fix 5: Use apt-get with Lock Timeout

# apt-get has built-in lock retry
$ sudo apt-get -o DPkg::Lock::Timeout=60 update

# Or set globally
$ echo 'DPkg::Lock::Timeout "60";' | sudo tee /etc/apt/apt.conf.d/99timeout

Prevention

Configure Automatic Retry

# Create apt config
$ echo 'DPkg::Lock::Timeout "120";' | sudo tee /etc/apt/apt.conf.d/99-lock-timeout

# For apt-get specifically
$ echo 'APT::Get::Lock::Timeout "120";' | sudo tee /etc/apt/apt.conf.d/99-lock-timeout

Schedule Updates Carefully

# Run updates during low-usage periods
$ sudo crontab -e

# Add (e.g., 3 AM Sunday)
0 3 * * 0 /usr/bin/apt-get update && /usr/bin/apt-get upgrade -y

Quick Commands

# Find lock holders
$ sudo fuser /var/lib/dpkg/lock-frontend
$ sudo lsof /var/lib/dpkg/lock-frontend

# Kill lock holders
$ sudo fuser -k /var/lib/dpkg/lock-frontend

# Check apt processes
$ ps aux | grep -E "apt|dpkg"

# View apt logs
$ sudo tail -f /var/log/apt/history.log
$ sudo tail -f /var/log/dpkg.log

Lessons Learned

Wait first, kill second - always check if the process is legitimately working.
Never force-remove locks while dpkg is running - it can corrupt your package database.
Use fuser -k as a safer alternative to manually removing lock files.
Configure DPkg::Lock::Timeout to handle temporary lock contention gracefully.
Check for unattended-upgrades - it runs automatically and holds locks.

This blog does not accept any external sponsorships, affiliate marketing, or ad revenue.