This bug was fixed in the package plymouth - 0.8.0~-13
---
plymouth (0.8.0~-13) lucid; urgency=low
[ Steve Langasek ]
* Don't attach /proc/cmdline to apport reports, this is already in the
standard info that gets collected...
[ Alberto Milone ]
* ubuntu_logo theme:
-
** Changed in: gdm (Ubuntu)
Status: New => Invalid
** Changed in: gdm (Ubuntu)
Importance: Undecided => Low
--
[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
GDM starts on VT1, however, no funny login interactions for me.
--
[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 maili
Can confirm, after disabling splash to get a working X experience from
bug #523788
--
[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.
--
08:25 < slangasek> architecture-wise, can you tell me what is *supposed* to be
happening in this case?
08:26 < Keybuk> plymouth is supposed to switch to vt7 and use a text plugin
that keeps the screen black until
passphrases are required, etc.
08:27 < Keybuk> this isn't all quite
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
** Summary changed:
- [lucid] gdm freeze at start
+ [lucid] if booting without 'splash', gdm starts X on wrong vt
** Also affects: gdm (Ubuntu)
Importance: Undecided
Status: New
--
[lucid] if booting without 'splash', gdm starts X on wrong vt
https://bugs.launchpad.net/bugs/518352
You
