Finally, somebody stumbled across a solution that worked also for me (http://ubuntuforums.org/showthread.php?p=8728987&posted=1#post8728987). The trick was to stop using CONCURRENCY=shell in /etc/init.d/rc and instead revert to CONCURRENCY=none.
But honestly, CONCURRENCY=shell is a long-running trick for speeding up boot on multi-core processors. I've even seen it in printed books in shops. And before applying it on my Karmic install (I've used it since Hardy), I did make sure the various web pages giving speed-tweak hints were still recommending it. And after all, it did work fine until around the time when Upstart 0.6.3-11 came. Downgrading Upstart didn't help me, though, so maybe one of the other updates around that time is what broke my system. I think somebody should follow up this a bit still. -- Services don't start on boot after Upstart update https://bugs.launchpad.net/bugs/511387 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
