Free tools Windows power users keep installed
One-click scans. No signup required.
This error usually means another package-management process is using APT or dpkg. Check which process holds the lock and let it finish; do not delete the lock file. If package configuration was interrupted, first ensure no package operation is still running, then run sudo dpkg --configure -a.
Why Ubuntu reports that it cannot get a dpkg lock
APT and dpkg use locks to prevent two package operations from changing package state at the same time. APT acquires a frontend lock as well as a dpkg administration lock; the frontend lock keeps competing package clients from starting while an operation is underway. See the APT implementation and the Ubuntu Foundations discussion.
The error may name /var/lib/dpkg/lock, /var/lib/dpkg/lock-frontend, or report that another process is using the frontend lock. These messages point to related but distinct lock paths. Read the full message: newer APT versions may identify the process ID and name, though wording varies by installed version.
1. Check whether another package operation is active
Look for an APT command in another terminal, Ubuntu’s graphical software updater, or an automatic update. An automatic unattended-upgrade is one documented example of a process that can hold lock-frontend; see this Ask Ubuntu example.
#1 Best Overall
If the process is carrying out a legitimate update or installation, let it finish. Starting or forcing another package operation while that work is active can cause problems.
2. Identify the lock holder if the message is unclear
Debian’s dpkg FAQ documents using fuser to inspect processes associated with lock paths. In a terminal, run it against the path named in your error, for example:
sudo fuser -v /var/lib/dpkg/lock-frontendFor an error naming the administration lock, inspect that path instead:
sudo fuser -v /var/lib/dpkg/lockReview the process information and establish what the process is before taking action. The Debian dpkg FAQ explains lock inspection and why the lock file itself is not proof that a process currently holds a lock.
Recommended Free Tools
3. Let normal work finish; do not delete the lock file
Do not run rm on /var/lib/dpkg/lock or /var/lib/dpkg/lock-frontend. As the Debian dpkg Team FAQ puts it, “Removing the dpkg lock files is never a correct solution”. The lock is associated with a process, and the file can remain on disk even when no process currently holds the lock. Removing it does not safely release an active process’s lock and can put package state or the filesystem at risk.
Do not blindly terminate a process just because it appears in the lock inspection output. Abruptly stopping package work may leave configuration incomplete. An expert-edited Ask Ubuntu answer gives community guidance on the risks of deleting lock files versus dealing with a process confirmed to be stuck.
Rank #4
4. Finish package configuration if an operation was interrupted
Only after confirming that no APT or dpkg operation is still running, use this command if dpkg reports that an earlier operation was interrupted or package configuration remains pending:
sudo dpkg --configure -aThis asks dpkg to configure unpacked but not yet configured packages. APT itself recommends the command when it detects an interrupted dpkg journal; the recommendation appears in the APT implementation, and the dpkg FAQ covers recovery guidance.
Best Value
Wait for the command to complete and read any error it prints. If it reports another active lock, return to checking the holder rather than removing a file or launching concurrent package commands.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
