© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
Colin points out this is probably related to bug #469354: dpkg-preconfigure doesn't take the dpkg lock, so if there's an aptd hanging around waiting for debconf answers, we'll get a collision on the debconf lock.
So there seem to be two parts to this bug:
- we need to figure out why there's an aptd hanging around waiting for debconf answers (possibly a UI bug?)
- we need to do more graceful error handling when there *is* something else holding the lock, since this may be legitimate - possibly by having dpkg-preconfigure try to take the dpkg lock instead and then recognizing this as a valid condition instead of crashing.