Bug 680235 - "plymouth-set-default-theme -R" fails
Summary: "plymouth-set-default-theme -R" fails
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 19
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-24 18:47 UTC by Horst H. von Brand
Modified: 2019-07-24 15:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 13:39:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Horst H. von Brand 2011-02-24 18:47:32 UTC
Description of problem:
# plymouth-set-default-theme -R
/usr/share/plymouth/themes//.plymouth does not exist

Version-Release number of selected component (if applicable):
plymouth-0.8.4-0.20110419.1.fc16.x86_64

How reproducible:
Always?

Steps to Reproduce:
1. plymouth-set-default-theme -R
2.
3.
  
Actual results:
/usr/share/plymouth/themes//.plymouth does not exist

Expected results:
Change theme? Where does thios file come from? Where is it documented?

Additional info:

Comment 1 jaguar981 2011-09-14 03:25:17 UTC
i have the exact same problem 
until i found this
su -
plymouth-set-default-plugin pluginname
/usr/libexec/plymouth/plymouth-update-initrd 

on 
http://www.my-guides.net/en/content/view/125/26/1/12/#plymouth

and that fixed the problem
im a newbie i hope that hellps

Comment 2 jaguar981 2011-09-14 03:48:22 UTC
edit: is plymouth-set-default-theme themename instead of plugin 
and instead of running 
plymouth-set-default-theme -R
run
/usr/libexec/plymouth/plymouth-update-initrd 
sorry for the errata

Comment 3 Fedora End Of Life 2013-04-03 17:25:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 4 William Penton 2013-07-04 17:41:07 UTC
I just upgraded from F18 using the 'fedup --network 19' command and I am trying to enable the plymouth themes but I am running into this exact error.

This is everything RPM/Plymouth related on this system.

[nexxuz@lappy486 ~]$ rpm -qa|grep plymouth
plymouth-theme-spinfinity-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-devel-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-system-theme-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-scripts-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-plugin-throbgress-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-plugin-space-flares-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-graphics-libs-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-core-libs-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-plugin-fade-throbber-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-theme-fade-in-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-theme-hot-dog-0.5-4.fc19.noarch
plymouth-plugin-two-step-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-plugin-script-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-theme-solar-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-theme-spinner-0.8.9-0.2013.03.26.0.fc19.i686
fedup-dracut-plymouth-0.7.3-1.fc19.noarch
plymouth-plugin-label-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-theme-charge-0.8.9-0.2013.03.26.0.fc19.i686
plymouth-theme-script-0.8.9-0.2013.03.26.0.fc19.i686

Please let me know if there is anything else you may need for this.

Comment 5 Matěj Cepl 2013-09-05 08:18:37 UTC
I would vote for NOTABUG (perhaps request-for-enhancement to Rawhide, but not a bug).

Looking at the --help output I get:

usage: plymouth-set-default-theme { --list | --reset | <theme-name> [ --rebuild-initrd ] | --help }

which to me clearly indicates that --rebuild-initrd REQUIRES explicit theme-name.

Comment 6 customercare 2014-06-27 09:59:39 UTC
FC20: Bug still prevails. 

##############################################################
IT'S CAUSED BY : /usr/libexec/plymouth/plymouth-update-initrd
##############################################################

It builds "initrd-3.14.8-200.fc20.i686+PAE.img" instead of "initramfs-3.14.8-200.fc20.i686+PAE.img". 

Guys, thats fixable in seconds !! How can that take YEARS to fix ? Honestly.

Comment 7 customercare 2014-06-27 10:09:00 UTC
FIX: check this bugreport #1113943 :

https://bugzilla.redhat.com/show_bug.cgi?id=1113943

Comment 8 Fedora End Of Life 2015-01-09 16:35:13 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Fedora End Of Life 2015-02-17 13:39:37 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.


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