Comment 6 for bug 224539

I'm gonna close this, marking it as Invalid. Any program that does apt work can have this 'failed to lock error', but there's no bug evident here. These are temporary problems, from running two package tools at once, or a process not exiting, or at worst a temporary file needing to be removed.

These reports show imperfections in the the packaging system that could be made into wishlist bugs:

- Jonas fixed his temporary problem. Ideally users would not have to manually clean up files to get past this.
- sirovsky was trying to do two package tasks at once. Perhaps error messages could make that clearer.
- oriman: did this continue? if this is reproducible for you, you might re-open this bug.

The error messages and cleanups could be improved, but receiving the "failed to lock" message isn't a particular breakage in update manager. Thanks.