I don't know how to verify it, but I can exclude tha last 2 entries as sudo
ls -la /dev/.initramfs returns the following:

root@Jarvis:/dev/.initramfs# ls -la
totale 0
drwxr-xr-x  2 root root   40 2010-02-25 13:14 .
drwxr-xr-x 16 root root 3880 2010-02-25 15:50 ..

I have also found this:

root@Jarvis:/var/log# grep plymouth daemon.log*
daemon.log:Feb 22 09:46:28 Jarvis init: plymouth-splash pre-start process
(1258) terminated with status 111
daemon.log:Feb 23 10:18:27 Jarvis init: plymouth-splash pre-start process
(1222) terminated with status 111
daemon.log:Feb 23 10:33:58 Jarvis init: plymouth main process (332) killed
by TERM signal
daemon.log:Feb 23 10:35:34 Jarvis init: plymouth main process (381) killed
by TERM signal
daemon.log:Feb 24 10:15:52 Jarvis init: plymouth main process (360) killed
by TERM signal
daemon.log:Feb 24 14:12:32 Jarvis init: plymouth main process (347) killed
by TERM signal
daemon.log:Feb 25 09:20:58 Jarvis init: plymouth main process (340) killed
by TERM signal
daemon.log:Feb 25 13:14:27 Jarvis init: plymouth main process (383) killed
by TERM signal
daemon.log.1:Feb 17 11:38:04 Jarvis init: plymouth main process (341) killed
by TERM signal
daemon.log.1:Feb 17 12:09:24 Jarvis init: plymouth-splash pre-start process
(1549) terminated with status 111
daemon.log.1:Feb 18 09:31:25 Jarvis init: plymouth-splash pre-start process
(1390) terminated with status 111
daemon.log.1:Feb 19 11:47:54 Jarvis init: plymouth-splash pre-start process
(1710) terminated with status 111
daemon.log.1:Feb 19 20:04:04 Jarvis init: plymouth-splash pre-start process
(1571) terminated with status 111
daemon.log.1:Feb 20 11:26:22 Jarvis init: plymouth-splash pre-start process
(1499) terminated with status 111
daemon.log.1:Feb 20 17:22:23 Jarvis init: plymouth-splash pre-start process
(1552) terminated with status 111
daemon.log.1:Feb 21 09:57:29 Jarvis init: plymouth-splash pre-start process
(1535) terminated with status 111

Please let me know if there's something else I can provide.

On Thu, Feb 25, 2010 at 11:13, Steve Langasek
<email address hidden>wrote:

> Yes, plymouth should fall back to the text plugin when not given
> 'splash', but you may have found a problem that's specific to the text
> plugin so I think we want to verify whether it happens when using
> splash.
>
> Also, if plymouth is running in the initramfs like it should be, it
> doesn't matter what start condition the upstart job lists, because the
> process should already be running.  So there are several possible causes
> here, none of which are reproducible for me:
>
>  - plymouth is not present in the initramfs
>  - plymouth is failing to start in the initramfs and cryptsetup is falling
> back to direct prompting for decrypting the root filesystem
>  - plymouth is starting, but exiting abnormally after decrypting the root
> filesystem
>  - plymouth is failing to write out the PID file to
> /dev/.initramfs/plymouth.pid
>  - the PID file is getting written, but isn't being transferred correctly
> when chrooting to the real filesystem
>  - the PID file is getting written, but upstart isn't picking it up
> properly
>
> Perhaps there's something you're seeing that suggests which of these is
> taking place, so we can narrow the search.
>
> --
> System does not booth with last plymouth. SAK needed to unlock it.
> https://bugs.launchpad.net/bugs/526321
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “plymouth” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: plymouth
>
> With plymouth 0.8.0~-10ubuntu1 my system does not boot. It hangs up after
> running initramfs-tools/scripts/init-bottom.
> Replacing the configuration file with the one that was in 0.8.0~-7 solved
> this.
> Seems like plymouth does not correctly handle (in init-bottom) the
> "post-start exec /bin/plymouth --show-splash " line, or that the missing
> "start on (starting mountall" tries to execute plymouth before mountall
> causing the system to hang.
>
> ProblemType: Bug
> Architecture: amd64
> Date: Tue Feb 23 10:39:39 2010
> DistroRelease: Ubuntu 10.04
> MachineType: Dell Inc. Vostro 1500
> NonfreeKernelModules: nvidia
> Package: plymouth 0.8.0~-10ubuntu1
> ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-14-generic
> root=/dev/mapper/sda6_crypt ro quiet
> ProcEnviron:
>  PATH=(custom, no user)
>  LANG=it_IT.utf8
>  SHELL=/bin/bash
> ProcFB: 0 VGA16 VGA
> ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
> SourcePackage: plymouth
> Uname: Linux 2.6.32-14-generic x86_64
> dmi.bios.date: 04/21/2008
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: A06
> dmi.board.name: 0WY040
> dmi.board.vendor: Dell Inc.
> dmi.chassis.type: 8
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.:bvrA06:bd04/21/2008:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr:
> dmi.product.name: Vostro 1500
> dmi.sys.vendor: Dell Inc.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/526321/+subscribe
>