Comment # 16 on bug 1169783 from t neo

(In reply to Robert Kaiser from comment #14)
> I found I can work around this by waiting for the timeout and enter the root
> password to get into the recovery console, then running:
> 
> systemctl start cryptsetup.target
> 
> The prompt appears and I enter the password for my /home partition (which is
> the one encrypted disk I have). Then I run this to get back to the normal
> system:
> 
> systemctl default
> 
> And then the system comes up correctly.
> 
> 
> Of course, this is an ugly workaround but at least the system can come up in
> some form in the mean time.

You can fix it permanently: 

In the file /usr/lib/systemd/system/systemd-ask-password-plymouth.service 

Change FROM:
ConditionPathExists=/run/plymouth/pid

TO:
ConditionPathExists=/var/run/plymouth/pid