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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/349469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
