OK, turns out the additions I made to the GDM init script still don't fix the gconf-sanity-check-2 error. It still happens, but it appears to be random. In fact, everything about these problems appears to be random. The synchronous nature of Upstart seems to make the boot process unpredictable, and when some programs look for things that SHOULD have been done before they started, but haven't because Upstart wants to do them all at once, things get messy. Besides, I thought Upstart was supposed to streamline the boot process and make it faster, but Karmic's boot process seems to be twice as long as any previous version.
-- Karmic boot doesn't wait for encrypted disc passphrase https://bugs.launchpad.net/bugs/468885 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
