http://bugzilla.suse.com/show_bug.cgi?id=1067503
http://bugzilla.suse.com/show_bug.cgi?id=1067503#c7
--- Comment #7 from Fabian Vogt
(In reply to Fabian Vogt from comment #5)
(In reply to Zhao Qiang 赵强 from comment #1) You probably don't, it's the wrong condition. Calling "dracut -f" is wrong anyway, it only recreates an initramfs for the currently running kernel, so if a new kernel got installed it'll keep the wrong theme.
The correct way IMO is: - Replace dracut -f in /usr/lib/plymouth/plymouth-update-initrd with mkinitrd -B - Don't call /usr/lib/plymouth/plymouth-update-initrd with -R in the .spec file - Instead, add %post %regenerate_initrd_post and %posttrans %regenerate_initrd_posttrans
That way it also won't do unnecessary initramfs rebuilds.
Thank you for your detailed support information. Yes, Replace with "mkinitrd -B" is also the reporter Mr. Giacomo focused on. But I still have a little concern: "mkinitrd -B" will make the initrd update but not refresh the bootloader, the user might need to refresh it manually. But this bug's real requirement is to assign the correct kernel edition which same as after installation. So, is there any help with the "-B" option? Sorry, I didn't follow you.
Refreshing the bootloader is not needed when calling just "plymouth-set-default-theme", which is the only way to end up in plymouth-update-initrd. The only place when refreshing the bootloader is really necessary is at the end of zypper runs, where the package's %posttrans takes care of it. -- You are receiving this mail because: You are on the CC list for the bug.