Comment 5 for bug 596560

We traced this back to yet another Upstart-related regression in Ubuntu Lucid. Now that Upstart is out of compatibility mode and has started to replace sysvinit in earnest, the old init scripts and the new are clashing and it's ugly.

IMHO, more could have been done to increase Upstart's compatibility with the old init scripts. The old init scripts already documented their dependencies for insserv, and with a bit of clever coding Upstart could have done something useful with that information, at least while we're still transitioning from the old system to the new. Flagging all reports of regressions as invalid isn't as helpful. Sigh. Ubuntu is infuriating sometimes.

For the record resolvconf really shouldn't be in universe. It's an infrastructural package closely related to the core networking scripts. That's the way it is in Debian, that's the way it should be in Ubuntu.

Anyhow, there's a fix for this that didn't make it into the LTS:

https://bugs.launchpad.net/ubuntu/lucid/+source/upstart/+bug/448095

Don't worry though, we'll incorporate this into the next release.