The problem here is Ubuntu devs are keen on starting GDM as soon as possible, to give the user the illusion of a faster bootup (just like Windows, I might add), while things keep loading in the background. Evidently there's a balance to be struck and we got caught in the "ugly" side of it.
It's a complicated thing to juggle all those initscripts and getting a setup that'll work on most/all configs. It's quite possible further optimizations can be made, but I'm not really sure what to touch anymore. Moving GDM after all the S20 stuff was easy and (probably) harmless, same with cupsys and foomatic/hplip (unless you do need cups active _before_ gdm, of course), but what about DBUS? HAL? Who knows? Not me, certainly. It's a bit sad that it took me this time to get off my behind and find this bug report, running Beta2 and RC1 as I was. -- Cannot run gdmsetup https://launchpad.net/bugs/66034 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
