I am not sure if plymouth or some other components should be selected... 
just my home partition is locked 

plymouth-0.8.3-11.el6.x86_64
dracut-004-24.el6.noarch
cryptsetup-luks-1.1.2-1.el6.x86_64
cryptsetup-luks-libs-1.1.2-1.el6.x86_64
kernel-2.6.32-44.el6.x86_64

seems to work here, but i'll do a fresh install

can you attach your /etc/crypttab and /etc/fstab ?

reading comment 0 carefully, it sounds like plymouthd may be crashing.  certainly no asterisks suggests that cryptsetup is reading the keyboard input and not plymouth.  Proposing for blocker until it's determined if this is a crasher or not.

vbenes can you attach those files please?

Created attachment 431692 [details]
fstab

Created attachment 431693 [details]
crypttab

I can see error like this: Couldn't start boot splash, no such file or directory

So what's probably going on here is you have a separate /usr partition

when you hit escape (or down arrow or whatever) in the brief window between when / and /usr are mounted the details plugin isn't available to get loaded and plymouth is probably croaking at that point.

We should make details be a "builtin" so it's always available.

yes, that's right I have my /usr dir on a separate partition

I'm building a version of plymouth now that builds details into the binary.

Please test this!  Since this involves the very early part of boot up, we really need to make sure this fix works and doesn't break anything else.

Still not fixed, but the behaviour is a bit better it works now unless you press up or down arrow (I use this keys to switch to console) while prompted for password.
After the arrow pressing the "Could not start boot splash: No such file or directory" error occurs and you are unable to fulfil the request.

It behaves as described above also if you are prompted for password in graphical mode and you press arrow

just to be sure, you did rebuild the initrd after installing the updated plymouth, right?

I'm looking through the patch and can't come up with a plausible explanation for the behavior you're describing.

I'll probably need to do a fresh install and reproduce to track this down.  Before I do that, I'd like confirmation from you that after installing the updated package you ran

/usr/libexec/plymouth/plymouth-update-initrd

or installed a new kernel.

(In reply to comment #14)
> just to be sure, you did rebuild the initrd after installing the updated
> plymouth, right?
> 
yes, I've installed new -54 kernel and also rebuild initrd with above command

> I'm looking through the patch and can't come up with a plausible explanation
> for the behavior you're describing.
>
the behaviour I see is this: wait until graphical password prompt is shown, press up/down arrow and try to enter the passphrase into text mode prompt.
I am unable to do this. No stars as I write just cursor jumps to next line and No key available with this passphrase" occurs after a while.

I did a guest install of plymouth with your configuration and was able to reproduce the problem.  The issue was that the Makefile lacked "-rdynamic" in its CFLAGS.

I never noticed this in local builds on my primary workstation, because I have -rdynamic in my default CFLAGS.

This is building now.

everything works as expected now, thanks for fixing it
-> VERIFIED

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.