Red Hat Bugzilla – Bug 1266085
rpm -V fails for /etc/plymouth/plymouthd.conf
Last modified: 2018-04-10 14:39:16 EDT
Description of problem: Ray identifies the cause in spec file (lines 410-417): %postun theme-charge export LIB=%{_lib} if [ $1 -eq 0 ]; then if [ "$(%{_sbindir}/plymouth-set-default-theme)" == "charge" ]; then %{_sbindir}/plymouth-set-default-theme --reset %{_libexecdir}/plymouth/plymouth-generate-initrd fi fi Version-Release number of selected component (if applicable): plymouth-0.8.9-0.21.20140113.el7 How reproducible: 100% Steps to Reproduce: 1. rpm -V plymouth\* 2. 3. Actual results: S.5....T. c /etc/plymouth/plymouthd.conf Expected results: no failure Additional info:
it's actually the %post section i think. export LIB=%{_lib} if [ $1 -eq 1 ]; then %{_sbindir}/plymouth-set-default-theme charge I believe the original motivation was to ensure charge gets set as the default theme if it's explicitly installed. These days plymouth will consult plymouthd.defaults so i think we can leave the admins config file alone.
Issue is still present in plymouth-0.8.9-0.30.20140113.el7 $ rpm -V plymouth S.5....T. c /etc/plymouth/plymouthd.conf
is it failing on fresh install or just upgrades? I don't think we can fix it easily for upgrades. We can't really repair the config file without potentially blowing away intentional changes.
This is only after update, on clean install the verification passes.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0999