© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
Interesting. So this looks like processes hanging around because they're waiting for users or other machines/network interaction. We probably need to handle this failure with a dpkg frontend that shows the user the current lock holder and gives them the option to break the lock and/or kill the holder.