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.
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.