I was thinking that if you remove “rhgb quiet” you stop the Fedora Logo showing and get the text scroll of the kernel events.
But is there some way to totally turn all that off? Suppose I want none of that to show until it gets to the SDDM login manager. So boot up would be =
grub menu → either pick a kernel with up/down arrow or timeout to the default kernel
(have screen be blank)
sddm login manager shows
Currently when I have “rhgb quiet” removed from the grub command line I don’t see the logo but I’m still getting the scroll of text, if you add “quiet” it seems to reduce some of the text but most is still there. I was looking into making a custom plymouth theme where the image is just all black but that seems a silly amount of work and I didn’t get it to work anyway.
So if someone knows I’d like to know how to completely obscure the Logo and the text listing
I tried that by making a clone of someone elses plymouth template at
since that theme was doing about exactly what I wanted other than the image not being black.
I then edited his files to make a new theme I called “boring”, by editing the image to just be all black,
the plymouth and script files were exact copies of his but simply with the name of the theme changed as needed to ‘boring’ like in the image file, etc.
I then made a folder at /usr/share/plymouth/themes/boring/ and put my files in there:
-rw-r–r–. 1 root root 234 May 8 14:06 boring.plymouth
-rw-r–r–. 1 root root 10637 May 8 14:06 boring.png
-rw-r–r–. 1 root root 315 May 8 14:06 boring.script
I then did this to register to the new theme
sudo plymouth-set-default-theme -R "boring"
/usr/lib64/plymouth/boring.so does not exist
and got that missing so file error. When I look in /usr/lib64/plymouth/ I don’t see a matching so file for each theme in /usr/share/plymouth/themes/ (which all came from Fedora except my ‘boring’ one) so I don’t get the problem. Does the so file get generated somehow if it’s custom made?
This isn’t anything I really need to work, I was just trying to figure it out because it might be a useful thing someday. The error is the “missing so file” in /usr/lib64/plymouth/
ps. on the baeldung.com instructions, there seems to be a flaw there. The instructions show the theme being copied to the themes folder but the theme is never actually registered. So there’d be no way for plymouth to know it’s supposed to use that theme over any of the others.
Usually you’d have to run