Red Hat Bugzilla – Bug 826765
plymouth-update-initrd has unexpected side effects
Last modified: 2013-08-01 06:10:06 EDT
Description of problem:
plymouth-update-initrd is a very ugly hack, having unexpected side-effects. It runs /sbin/new-kernel-pkg in a way that seems to do more than it should. --install seems not to be a good choice since it creates new entries in grub2.cfg. Also note that it uses the hardcoded argument --package kernel, no matter if you are actually running kernel-PAE. apparently, new-kernel-pkg offers --add-plymouth-initrd, which, however, seems not to have dracut support yet. Why not implement dracut support for --add-plymouth-initrd and use it?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
new toplevel entry in grub2.cfg
Only a dracut run is triggered that updates the initramfs of the running kernel, and other things necessary for updating plymouth related stuff, and nothing else.
See also bug 624601. This problem will probably be triggered by running plymouth-set-default-theme, too.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
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 prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.
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.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.