Since last-good-boot and kernel-helper are all gone, replaced
(conceptually) with smarter code in grub2, this is no longer an issue;
and the offending code in oem-config-firstboot was removed long ago.
** Changed in: ubiquity (Ubuntu)
Status: Triaged = Won't Fix
--
You received this bug
** Package changed: oem-config (Ubuntu) = ubiquity (Ubuntu)
** Tags added: oem-config
--
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.
--
This is no longer a problem for Intrepid since Ben has disabled last-
good-boot by default. It may be a problem for future releases if it
continues to use update-grub and update-grub continues to use debconf in
all modes.
** Changed in: oem-config (Ubuntu Intrepid)
Status: Triaged = Won't
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
It's not *that* awful ;)
It's quite racy though, since kernel-helper could actually start as you
get to done and then you'll have exactly the same problem.
--
awful hack to avoid kernel-helper debconf clash
https://bugs.launchpad.net/bugs/261543
You received this bug notification because you
Perhaps the real problem is that using debconf asynchronously during the
boot sequence is not in fact an excellent plan composed solely of
kittens.
--
awful hack to avoid kernel-helper debconf clash
https://bugs.launchpad.net/bugs/261543
You received this bug notification because you are a
Racy: yes, that was pretty much exactly my point, though perhaps I could
have spelled it out more clearly. I suppose I figured anyone competent
to change that code would see the pidof and recognise this. :-)
--
awful hack to avoid kernel-helper debconf clash
Actually I was more thinking that your code waits for a condition to
become false before continuing, on the assumption that it has been true
at some point in the past.
When in fact, the very nature of asynchronousity means that the
condition may be yet to become true when this code runs.
Upstart
