text theme. Boot never finishes, waiting for plymouth-quit-wait.service forever. System is mostly up, but plymouth doesn't want to terminate and the systemd never enters multiuser mode. [root@shorty ~]# systemctl list-jobs 86 getty.target start waiting 87 getty start waiting 92 getty start waiting 94 getty start waiting 96 getty start waiting 98 getty start waiting 107 plymouth...t-wait.service start running [root@shorty ~]# ps -ef | grep plymouth root 191 1 0 08:11 ? 00:00:04 /bin/plymouthd --attach-to-session --pid-file /run/plymouth/pid root 2750 1 0 08:11 ? 00:00:00 /bin/plymouth --wait root 3231 2891 0 08:21 pts/1 00:00:00 grep --color=auto plymouth [root@shorty ~]# strace -p 191 Process 191 attached - interrupt to quit epoll_wait(3, [hangs] Removing rhgb from the kernel boot prompt does not work. plymouth still gets stuck: [root@shorty ~]# ps -ef | grep plymouth root 916 1 0 08:23 ? 00:00:00 /sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid root 2761 1 0 08:24 ? 00:00:00 /bin/plymouth --wait root 2891 2878 0 08:24 pts/0 00:00:00 grep --color=auto plymouth
Created attachment 502979 [details] I don't see anything interesting in /var/log/boot.log
What plymouth theme are you using? If you're using spinfinity, this sounds like bug #704658.
text theme
I think I see the same problem occurring randomly with the default theme (charge?). It might possibly be caused by taking too long to enter the password for the encrypted partition, but I'm not entirely sure what the timeout is there. If I SSH in, and issue `plymouth quit`, then everything continue as normal.
I'm on F17 - an upgrade from F15 and I'm having the exact same problem. Killing or running plymouth quit allows gdm to show the login window. If anyone can suggest ways to debug this I would gladly help out. I'm a bit lost - no errors found in any logfile.
what version of gdm? GDM normally runs "plymouth quit" itself.
(In reply to comment #6) > what version of gdm? > > GDM normally runs "plymouth quit" itself. $ rpm -q gdm gdm-3.4.1-3.fc17.x86_64
and what does your plymouth theme look like? is it a sideways 8 or a fedora logo filling up ?
(In reply to comment #8) > and what does your plymouth theme look like? > > is it a sideways 8 or a fedora logo filling up ? I'm using the infini-spinner - not the default. But I have that running on other boxes without the freeze.
cat /etc/plymouth/plymouthd.conf # Administrator customizations go in this file #[Daemon] #Theme=fade-in [Daemon] Theme=spinfinity
there was a bug though (see comment 2) in spinfinity that can cause exactly the issues you're seeing. I'd recomment upgrading your plymouth package to the latest in updates and then rebuilding your initrd (with dracut -f or /usr/libexec/plymouth/plymouth-update-initrd) and see if that corrects your issue.
$ sudo /usr/libexec/plymouth/plymouth-update-initrd grubby fatal error: unable to find a suitable template
sudo dracut -f seems to have done it. It's still a long wait with lots of IO between the boot-process completing and gdm showing the login screen - but it doesn't hang anymore. Thanks - not sure if the plymouth-update-initrd issue is a concern. I got that error during my upgrade too.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping