Ok, thanks. If you boot without 'splash', there's an unfortunate interaction between plymouth and gdm. gdm checks if plymouth is running, to decide whether it can use the same VT as plymouth to start its first X server; but when booting without splash, plymouth never changes VTs, which means that gdm will start X on VT1 - which will conflict with the getty that is started there.
I'm not sure what the right way will be to solve this - either plymouth can switch VTs even when not using 'splash', but that might defeat the purpose of the nosplash handling; or plymouth can add a way for gdm to ask if the boot splash is active, and not answer 'yes' in this case. Termina, since you are booting *with* splash, you should file a separate bug report for your issue. -- [lucid] if booting without 'splash', gdm starts X on wrong vt https://bugs.launchpad.net/bugs/518352 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
