Comment # 51 on bug 1169783 from J Merkel

(In reply to J Merkel from comment #49)
> A question for clarification, hoping some of you could answer.
> I'm not (yet) affected by this bug, because I've stopped updating when I saw
> this bug report on the mailing list.
> All 3 partitions on my TW installation are encrypted, and I've configured
> the system i.e. grub to ask only once for the passphrase, all three
> partitions are then unlocked by a keyfile provided in cryptab later in the
> process.
> I do not see plymouth involved in this case so, in case I would do an
> upgrade would the configuration I've described be affected at all by the bug
> ?

To answer myself for the sake of others in similar situation:
My assumption was right, I did an upgrade to 20200428, my config boots without
problem.
Plymouth is showing the three dots while decrypting the drives but is not
screwing the boot process.

Why on earth is plymouth being used on TW - a (b)leading edge rolling release
where probably most users want to see the diagnostics at boot and push the ESC
key anyhow???