There actually is a lock; the problem is waiting for it to be free rather than just falling over. The fact that the lock is taken out deep in the internals of debconf and the result of it failing is a message on stderr and an exit code, not a nice exception, doesn't help.
You're probably right that waiting for the lock is the right answer though (short of making last-good-boot not use debconf in the boot sequence in the first place!). Thanks. -- awful hack to avoid kernel-helper debconf clash https://bugs.launchpad.net/bugs/261543 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
