Bug 1304795

Summary:	RFE 'plymouth-set-default-theme -R' should call 'dracut -f'
Product:	[Fedora] Fedora	Reporter:	Raphael Groner <projects.rg>
Component:	plymouth	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	elad, fedora, rstrode
Target Milestone:	---	Keywords:	FutureFeature, Reopened
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-06 06:24:37 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:

Description Raphael Groner 2016-02-04 15:57:41 UTC

Description of problem:


Version-Release number of selected component (if applicable):
plymouth-0.8.9-10.2013.08.14.fc22
plymouth-scripts-0.8.9-10.2013.08.14.fc22

How reproducible:
yes

Steps to Reproduce:
1. dnf install plymouth-theme-spinfinity
2. plymouth-set-default-theme spinfinity -R
3. dracut -f
4. reboot
5. plymouth-set-default-theme -r -R
6. reboot (and do not call dracut)

Actual results:
still spinfinity plymouth boot splash shown at boot

Expected results:
plymouth boot splash is reset to default

Additional info:
Manual workaround is to call dracut -f in a root terminal.

No idea if that happens also in Fedora 23, I've not tested this. At least, it must be fixed in Fedora 22. According to koji, Fedora 23 has a newer release, can you build that for F22?

Comment 1 Raphael Groner 2016-02-04 16:08:56 UTC

Possible duplication: bug #1059485

Comment 2 Fedora End Of Life 2016-07-19 20:16:21 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Raphael Groner 2017-03-06 06:24:37 UTC

This seems to be fixed in Fedora 25. Please feel free to reopen if you think it's still an issue.