I've lost remote computer entirely after changing plymouth theme:

  sudo plymouth-set-default-theme futureprototype
  sudo update-initramfs -u -k all

("futureprototype" was one of the available themes according to "--list").

That was on linux-image-686, fully dist-upgrade'd to Buster
after switching from previous theme "spacefun".

All commands executed successfully and without warnings yet after reboot all
kernels drop into busybox shell, including recovery GRUB options rendering
computer unbootable.

I had no idea that using plymouth could be so dangerous. :(
---

The cure for the evils of democracy is more democracy.
        -- H. L. Mencken

Le 6/10/19 à 10:35, Dmitry Smirnov a écrit :
Do you see any specific error?

Does is boot if you remove the "splash" from the kernel cmdline? Can you
try to explicitly disable plymouth with "plymouth.enable=0" ?

Can you list the files installed in the initramfs with lsinitramfs?

No... The computer is on another continent with unskilled operator...
I've got as much information as I could obtain under the circumstances.

It does not boot. That's the first thing we tried by going to recovery option
in GRUB.

Unfortunately that won't be possible unless I manage to reproduce the problem
on pristine system.

Impossible. As I've said access to computer was lost. Previously I could only
access it remotely... But it was pretty much in default state without any
customisations or DKMS kernel modules. The only non-default thing there was
previous "spacefun" theme that worked perfectly until change to
"futureprototype".

---

One has to multiply thoughts to the point where there aren't enough
policemen to control them.
        -- Stanisław Jerzy Lec