Setting to triaged, as this is easily reproducible and not hardware
dependent. Confirming "high" priority as it makes fsck and cryptsetup
messages absolutely unreadable.
My first hunch was that this was related to natty's PNG optimization,
but it's not. Just downgrading libplymouth2 (which doesn't have any
graphics) to the maverick version makes it work, even with the optimized
PNGs in plymouth-ubuntu-theme-logo; conversely, building plymouth
without pkgbinarymangler doesn't fix it.
For the record, this can be used to test it with plymouth-x11, which is
easier than rebooting or starting plymouth on a VT:
--------------------- 8< -----------------
[ `id -u` = 0 ] || {
echo "Please run this as root" >&2
exit 1
}
(plymouthd --no-daemon --debug &)
sleep 1;
plymouth --show-splash
sleep ${1:-3}
plymouth --quit
--------------------- 8< ------------------
** Changed in: plymouth (Ubuntu Natty)
Status: Confirmed => Triaged
** Changed in: plymouth (Ubuntu Natty)
Milestone: None => ubuntu-11.04-beta
** Changed in: plymouth (Ubuntu Natty)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
** Summary changed:
- plymouth2_0.8.2-2ubuntu6 and later give ragged splash and text rendering
+ libplymouth2_0.8.2-2ubuntu6 and later give ragged splash and text rendering
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685352
Title:
libplymouth2_0.8.2-2ubuntu6 and later give ragged splash and text rendering
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
