The Plymouth bug resulted in my install failing to boot. Holding the grub shortcut to show the boot menu did not work, so I had to boot from a USB, decrypt the drive, mount the logical volumes, chroot, update the bootloader config and regenerate the bootloader, restart into a snapshot and restore.
I had relied on being able to access grub as per the documentation though and was only a little surprised when it flat out didn’t work. There’s a lot of polish missing all over the place.
Definitely not something that your average user would be able to recover from themselves. There seems to be a gap in testing there, and some questionable decisions that the splash screen can prevent boot.
You asked if anyone had encountered this bug. I use tumbleweed and did encounter it. I would happily see more people using Linux, but for that to happen we need to acknowledge the areas that need improvement, rather than just blithely claiming they are pushing an agenda.
Tumbleweed is incredible, it doesn’t make the tradeoffs with outdated packages that leap has and is usually very stable, but in this case there may be some test cases or processes that might help improve it even further.
When slowroll is more mature I plan on switching to that to hopefully avoid these types of problems.