The boot log shows the filesystem event has been emitted, and that udevtrigger has stopped; and the initctl output shows that dbus is running. Those are all the preconditions for starting gdm, so the job should have stopped - though we don't see this in the boot log because starting gdm will stop plymouth.
Can you try running 'sudo start gdm' by hand from the console immediately after boot, and report the results? Also, can you attach /var/log/syslog? -- gdm fails to start sitting on plymouth boot https://bugs.launchpad.net/bugs/577477 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
