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
}
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 &) ------- ------- 8< ------------------
sleep 1;
plymouth --show-splash
sleep ${1:-3}
plymouth --quit
-------