When this happens, dpkg sets a "lock" and flags itself as "broken." It refuses to process any new requests until the previous job is completed or cleaned up.

Sometimes, running sudo dpkg --configure -a isn't enough. You might see the error persist, or you might encounter new errors relating to "dependency problems."

This means another process (like an automatic update, Software Center, or another terminal) is using the package system. Use:

Dpkg Was Interrupted You Must Manually Run Sudo Dpkg Configure To Correct The Problem

When this happens, dpkg sets a "lock" and flags itself as "broken." It refuses to process any new requests until the previous job is completed or cleaned up.

Sometimes, running sudo dpkg --configure -a isn't enough. You might see the error persist, or you might encounter new errors relating to "dependency problems." When this happens, dpkg sets a "lock" and

This means another process (like an automatic update, Software Center, or another terminal) is using the package system. Use: When this happens