[grischa@desktop-wg ~]$ sudo systemctl enable plymouth-start.service |fpaste
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit’s
.wants/ or .requires/ directory.
• A unit’s purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, …).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
No text to send.
If you do a “systemctl status plymouth-start.service” you’d see that it is a “static” service as listed in the “Possible reasons” output you’ve shown. Static services are not meant to be “enabled”. As stated, there is a symbolic link in sysinit.target.wants pointing to the service.
Try rpm -Va plymouth\* . This will check the integrity of your installation of all Plymouth packages against correct values. If you get any lines back, particularly one for plymouth-start.service with a “5” in the leading periods, run sudo dnf reinstall plymouth\* .
You may need to run sudo dracut -vf --regenerate-all afterwards. I don’t know if Plymouth is run from initramfs or not, but you have to do that after changing themes in Plymouth, so maybe.
Edit: The “*” is optional. It appears to be an issue with just the main package.
Edit 2: This all looks unnecessary. It doesn’t look like anything is wrong.
Run grep "rhgb quiet" /etc/default/grub to check if it should be getting into grub’s config based on your settings. I’ll presume that you won’t get a result and in which case you should add “rhgb quiet” to the end of the “GRUB_CMDLINE_LINUX” line in /etc/default/grub.
If you do get something from grep, run sudo grep "rhgb quiet" /boot/efi/EFI/fedora/grub.cfg.