Comment 16 for bug 509487

Here you go, looking at it, I guess your next question would be this one:
root@castiana:/root# ls -l /lib/plymouth/label.so
-rw-r--r-- 1 root root 10464 2010-01-11 08:52 /lib/plymouth/label.so
root@castiana:/root# ls -l /lib/plymouth/themes/ubuntu-logo/
total 56
-rw-r--r-- 1 root root 870 2010-01-11 08:52 box.png
-rw-r--r-- 1 root root 296 2010-01-11 08:52 bullet.png
-rw-r--r-- 1 root root 350 2010-01-11 08:52 entry.png
-rw-r--r-- 1 root root 1896 2010-01-11 08:52 lock.png
-rw-r--r-- 1 root root 199 2010-01-11 08:52 progress_bar.png
-rw-r--r-- 1 root root 215 2010-01-11 08:52 progress_box.png
-rw-r--r-- 1 root root 233 2010-01-11 08:52 ubuntu-logo.plymouth
-rw-r--r-- 1 root root 28008 2010-01-11 08:52 ubuntu-logo.script

Also, I noticed something weird that I'm not sure is related or not.
When booting with no mountpoint requiring a luks volume (basically how I boot at the moment by commenting the right line in my fast), cryptsetup seems to start anyway in the background and waits for a key. Only issue is that plymouth never asks for that key and boots as if no key was needed at all (it's actually right as no mountpoint require it but then cryptsetup shouldn't start either).

A quick "ps aux" after a boot with all encrypted partitions commented out in my fstab (but the luks volume present in crypttab):
root 1719 0.0 0.0 3980 568 ? S 01:16 0:00 /lib/udev/watershed /lib/cryptsetup/askpass Unlocking the disk /dev/disk/by-uuid/851db151-043d-46fd-9632-626d6f57bb86 (sda2_crypt)\nEnter passphrase:
root 1720 0.0 0.0 19204 2844 ? S<L 01:16 0:00 cryptsetup --key-file=- luksOpen /dev/disk/by-uuid/851db151-043d-46fd-9632-626d6f57bb86 sda2_crypt_unformatted
root 1722 0.0 0.0 3848 444 ? S 01:16 0:00 /lib/cryptsetup/askpass Unlocking the disk /dev/disk/by-uuid/851db151-043d-46fd-9632-626d6f57bb86 (sda2_crypt)\nEnter passphrase:

As I mentioned, plymouth simply completely ignores that and boot to gdm as if nothing happened :)