usplash is as good as it's going to get in this regard for Karmic. Right
now, the flicker will be the brief switch back to text mode, now fairly
reliably on tty1, before usplash kicks in. I think it is now briefer
than before and probably with fewer junk messages, but that's about it.
The fundamental problem here is that X is quite insistent about
switching back to the console it started on, and restoring the state of
that console. This means that (a) if you start X without shutting down
usplash first, you get switched back to a corrupted console if you try
to use Ctrl-Alt-F[1-6]; and (b) X will always switch back to tty1, and
trying to start usplash before it does so achieves very little since
they have a bit of a deathmatch and you usually end up on a text console
at best.
Now, you might say that none of this should be a problem with KMS, and
you'd probably be right. However, X doesn't seem to have been educated
in the fact that it doesn't need to do mode restoration when we switch
away from its VT (or else something else is going on), and in any case
we'd still need to arrange the Upstart jobs such that they don't break
systems using video drivers not yet converted to KMS.
We'll look at this further for Lucid, since the underlying problem
affects both boot and shutdown.
** Changed in: usplash (Ubuntu Karmic)
Status: Triaged => Won't Fix
** Changed in: usplash (Ubuntu Karmic)
Milestone: ubuntu-9.10 => None
** Changed in: usplash (Ubuntu)
Milestone: ubuntu-9.10 => None
--
Text console messages are displayed briefly during shutdown
https://bugs.launchpad.net/bugs/348440
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
