unl0kr does not work if plymouth is enabled

[gradientvera]

Describe the bug

unl0kr does not work if plymouth is also enabled.

Steps To Reproduce

1. Set boot.plymouth.enable to true
2. Set boot.initrd.unl0kr.enable to true
3. Rebuild system and reboot
4. unl0kr "crashes" and gets replaced by the plymouth decryption screen.

Expected behavior

unl0kr stays on screen and is usable, instead of being replaced by plymouth

Additional context

For some reason, after this happens plymouth cannot get any text input either, even though normally (without unl0kr enabled) it works just fine.
Also, I have been unable to gather logs during this whole process yet, as I cannot figure out how.

Notify maintainers

@tomfitzhenry

Metadata

I am running Jovian-NixOS and haven't tested this bug on a regular system (yet) but I doubt it matters.
Replicated with a regular machine too.
Also using systemd-boot.

~ >>> nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.52-valve17, NixOS, 24.05 (Uakari), 24.05.20240224.73de017`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.19.3`
 - nixpkgs: `/etc/nix/inputs/nixpkgs`

---

Add a 👍 reaction to issues you find important.