RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1266085 - rpm -V fails for /etc/plymouth/plymouthd.conf
Summary: rpm -V fails for /etc/plymouth/plymouthd.conf
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: plymouth
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-24 12:45 UTC by Tomas Pelka
Modified: 2018-04-10 18:39 UTC (History)
1 user (show)

Fixed In Version: plymouth-0.8.9-0.29.20140113.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 18:38:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0999 0 None None None 2018-04-10 18:39:15 UTC

Description Tomas Pelka 2015-09-24 12:45:14 UTC
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:

Comment 1 Ray Strode [halfline] 2015-09-24 12:51:52 UTC
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.

Comment 3 Jiri Koten 2017-11-30 16:11:35 UTC
Issue is still present in plymouth-0.8.9-0.30.20140113.el7

$ rpm -V plymouth
S.5....T.  c /etc/plymouth/plymouthd.conf

Comment 4 Ray Strode [halfline] 2017-11-30 16:43:55 UTC
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.

Comment 5 Jiri Koten 2017-12-01 13:06:11 UTC
This is only after update, on clean install the verification passes.

Comment 10 errata-xmlrpc 2018-04-10 18:38:54 UTC
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


Note You need to log in before you can comment on or make changes to this bug.