Red Hat Bugzilla – Bug 840322
non-existent plymouth stay running during OS life
Last modified: 2013-08-01 06:19:11 EDT
Description of problem:
Although I uninstall all plymouth-* packages, after reboot there is all the time plymouthd process:
# ps xaw|grep plym
153 ? S 0:00 /bin/plymouthd --attach-to-session --pid-file /run/plymouth/pid
Version-Release number of selected component (if applicable):
plymouthd should not be running/stay running
I suppose that process was running from initramfs ("/bin/plymouthd" not exist on root fs) and perhaps after creating new initramfs from dracut this program will not be at initramfs too (and thus can it not be running), but what if I never create new initramfs? More, even if it is still present in initramfs, I have no "rhgb" parameter on kernel commandline - thus I think isn't any reason for its starting.
i must refine this issue: it seems as from initramfs running plymouthd has attached console (/dev/tty1) and is impossible login at it.
But i was able switch to other /dev/ttyX with ALT/Fx, and there keyboard input work and login is possible.
Also, killing plymouthd process help and /dev/tty1 is acessible from keyboard.
try rebuilding your initramfs with
plymouth gets started before your root filesystem is mounted.
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.