Comment # 15 on bug 1148242 from ravas mi

So following from my YaST uninstall of the two packages, I looked at the output
of "lsinitrd" and found a lot of plymouth stuff still in there. I guess that's
why the boot loaded lightdm without a problem. I then ran `dracut --force
--omit "plymouth"`, which effectively cleaned the initramfs of all mention of
plymouth. I rebooted and lightdm failed to load. So it seems like some aspect
of plymouth needs to be in the initramfs -- otherwise this problem manifests.
I've noticed "plymouth-quit.service" is mentioned in "display-manager.service"
under "After=", "Conflicts=" and "OnFailure=" (hence the journal message).

I reinstalled plymouth and lightdm loaded fine. No surprise at this point.

I'm just going to leave plymouth installed and use "plymouth.enable=0", which
worked fine for several days; although, I won't consider this resolved until we
understand why plymouth as become a pseudo-dependecy.