I think the problem is that the procps postinst in maverick uses 'start procps' rather than 'invoke-rc.d procps start || exit $?' as is used in precise. See bug 602896 for the fix.
This is a pre-existing bug in maverick, but it was dormant because the installer didn't need to upgrade procps in this phase of installation until now. I think the fix for bug 602896 needs to be backported to maverick-proposed. This bug was fixed in natty, and, oddly, lucid didn't suffer from it in the first place because it doesn't appear to start the procps job in the postinst at all. ** Tags added: verification-failed-maverick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771372 Title: procps runs too early in the boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/771372/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
