This bug was fixed in the package plymouth - 0.8.0~-6
---------------
plymouth (0.8.0~-6) lucid; urgency=low
* Revert change in 0.8.0~-4 that scans the buffer out fo fbcon when
deactivating i915; this was actually wrong, we don't want to use fbcon
for the transition, we want to use our current framebuffer instead.
Other bugs (with the VT code) are preventing that transition from working.
* Fix a crash on "plymouth deactivate" when no renderer is active.
LP: #499541.
* Fix a crash on "plymouth deactivate" when --show-splash has never
been called.
* Fix failure to quit on "plymouth quit" after "plymouth deactivate".
* Remove the code that disables plymouth when init= is on the command-line,
we don't want that.
* debian/initramfs-tools/scripts/init-top/plymouth:
- Don't check the kernel command-line; we always want plymouth running
whether or not "splash" is present, plymouth uses that to determine
which of the graphics or text renderers to use.
- Start with --attach-to-session so we redirect console messages.
* debian/plymouth.plymouth-log.upstart:
- Once the filesystem is mounted, flush the log out.
-- Scott James Remnant <sc...@ubuntu.com> Wed, 23 Dec 2009 03:54:42 +0000
** Changed in: plymouth (Ubuntu)
Status: Triaged => Fix Released
--
plymouth segfault with nvidia graphics
https://bugs.launchpad.net/bugs/499541
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
