[Natty] New plymouth does not get loaded

on i386 i'm using 0.8.2-2ubuntu16 & nvidia 260.19.21-0ubuntu3, compiz not installed

booting without "quiet splash", i'm seeing 2 plymouth errors at the very beginning:
- plymouth have stopped with error status 29
then 2 lines later:
- plymouth have stopped with error status 1

then the boot process continue as it have to do. As it never boot the first time, i suppose it have something wrong with upstart.

Confirmed with pinned/locked X-server version 1.9.2 and nVidia driver 270.18

I had the same problem, totally breaking bootup since I cannot enter the password for my crypted homevolume anymore.

But: It seems to be kernel related. linux-image-2.6.38-3-generic 2.6.38-3.30 is broken for me, when I change to linux-image-2.6.38-2-generic 2.6.38-2.29 it works again. amd64 platform, Intel graphics

How to boot an encrypted disk with the plymouth "Black Screen of Death" bug:

OK, let's assume you have only one kernel and only one initramfs. If you have older kernels installed, their initramfs images contain the older versions of plymouth unless you ran update-initramfs -u -k all by hand at some point. Doing this on a non-encrypted machine or after unlocking from Busybox, of course, would be a definitive test to see if this is kernel related at all.

With splash removed from the command line, your console works but cryptsetup's "cryptroot" script obviously does not. Neither does the custom script I use to unlock many disks from one password, for that matter. Init's root volume search will time out, and a Busybox shell will spawn. Now you can run cryptsetup manually, and it works fine, exactly like unlocking but not mounting an encrypted flash drive from the command line.

 If you arre not using LVM on your encrypted volume, you must remember the exact name of the root device from /proc/cmdline or use cat /proc/cmdline to bring it up. If you are using LVM, any name for the /dev/mapper device will work, though you still need the correct source device. Your root device now exists, so your next command is "exit" causing Busybox to terminate and the boot process to resume. Now you can roll Plymouth back or your kernel back even if you only had one kernel installed(a bad idea on any alpha).

I have same problem as Bernhard Schmidt: it seems new kernel broke something for intel graphics... Will open new bug, as this is probably separate issue.

I have opened a kernel bug for my intel graphics problem - bug 718562

comment into post #1 ( error status 29 ) above is wrong: i get both on startup & shutdown: terminated with status 69

I'm having the same problem with 2.6.37-020637-generic (v2.6.37-natty from kernel-ppa), also in connection with Intel graphics on a Thinkpad.
Downgrading plymouth to 0.8.2-2ubuntu14 did work although I'm not getting any text telling me to enter the disk password, however the textbox is there and I can enter the password and booting proceeds as it should.

This bug was fixed in the package plymouth - 0.8.2-2ubuntu17

---------------
plymouth (0.8.2-2ubuntu17) natty; urgency=low

  * Rework the avoid-sigpipe patch to first attempt to use send(), and
    then fall back to write in case of ENOTSOCK. (LP: #718044).
 -- Soren Hansen <email address hidden> Mon, 14 Feb 2011 13:30:00 +0100

Confirming the fix works.