How to Fix "Could Not Get Lock /var/lib/dpkg/lock" Error in Linux

By Emily Watson Jul 6, 2026 6 min read How-To Guides

The "Could not get lock /var/lib/dpkg/lock" error appears when another process is using the package manager. This is a common frustration for Linux beginners. Here is how to resolve it safely.

Fix 1: Wait for the Other Process to Finish

The most common cause is that you have another terminal open running an apt command, or a software updater is running in the background. Close all other terminal windows and check if Update Manager or Software Center is running. Wait for any ongoing update to complete, then try again.

Fix 2: Kill the Stuck Process

If no other terminal is open but the lock persists, a process may be stuck. Run sudo lsof /var/lib/dpkg/lock to find the process ID (PID) holding the lock. Then run sudo kill -9 PID to force-stop it. After killing the process, run sudo dpkg --configure -a to clean up any interrupted operations.

Fix 3: Remove the Lock File Manually

If killing the process does not work, you can remove the lock file. Run sudo rm /var/lib/dpkg/lock and sudo rm /var/lib/apt/lists/lock. Then run sudo dpkg --configure -a followed by sudo apt update. Warning: only do this if you are sure no other apt process is running, as removing the lock during an active operation can corrupt your package database.

How to Prevent This Error

To avoid lock errors in the future, always close Software Center and Update Manager before using apt in the terminal. Only run one apt command at a time, and let it finish completely. Use sudo apt install instead of sudo dpkg -i for most installations, as apt handles dependencies better.