Bug 1530727

Summary:	default plymouth theme is not set in RHEL 7.5 Beta
Product:	Red Hat Enterprise Linux 7	Reporter:	Oliver Ilian <oliver>
Component:	plymouth	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.5	CC:	bgollahe, jkoten, tpelka
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	plymouth-0.8.9-0.31.20140113.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 18:38:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1527213

Description Oliver Ilian 2018-01-03 16:54:23 UTC

Description of problem:
In RHEL 7.4 charge is the default plymouth theme during boot. In RHEL 7.5 no theme is set and leaves a rather ugly boot screen.

Version-Release number of selected component (if applicable):
RHEL 7.5 Beta

How reproducible:
always

Steps to Reproduce:
1. Install RHEL 7.5 Beta and reboot

Actual results:
plymouth does not show the same theme as in RHEL 7.4 (charge)

Expected results:
plymouth should still set the default theme to keep the boot experience the same for all RHEL 7.x releases.

Comment 2 Ray Strode [halfline] 2018-01-03 18:15:59 UTC

eek, maybe a regression from bug 1266085

Comment 4 Ray Strode [halfline] 2018-01-08 15:28:56 UTC

i've reintegrated the scripts from bug 1266085 in a condensed form and switched tacts to using %verify on the configuration file.

Comment 9 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