Something happened and now bootup takes about 10 minutes.
# cat /etc/issue
Fedora release 17 (Beefy Miracle)
Kernel \r on an \m (\l)
when I run "systemctl --failed"
I get
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
plymouth-quit-wait.service loaded failed failed Wait for Plymouth Boot Screen to Quit
# systemctl status plymouth-quit-wait.service
p
I have been having issues with Fedora 17 not booting after the latest round of updates. I am able to enter the pass for my disk encryption, the boot logo acts normally but after the animation is complete, the boot fails to progress further.
I checked the diagnostics and it seems that there is an issue in plymouth-quit-wait.service.
I have been having issues with Fedora 17 not booting after the latest round of updates. I am able to enter the pass for my disk encryption, the boot logo acts normally but after the animation is complete, the boot fails to progress further.
I checked the diagnostics and it seems that there is an issue in plymouth-quit-wait.service.
Not really sure where this goes so admins feel free to move it. I am running Fedora 17 and recently upgraded to the 3.6.10-2.fc17.x86_64 kernel at the time I upgraded I had to remove some nvidia stuff and then upon rebooting my system would hang.
Hello,
I am trying kernel 3.7 vanilla into fedora 17 i686
When boot, the system shows
Failed to start Wait for Plymouth Boot Screen to Quit
My f17 is current using nouvea drivers, and when i am looking into the dmesg i got a
enable_msi not found
if i remove all xorg config file to nouvea, still not working ...
any clues?
tx
Hi allm,
About 2 or 3 upgrades ago (on Fedora 17) my machine starting hanging on boot, just after quitting the plymouth splash screen.
It looks like the Xserver is trying to start ,but gets stuck: an X cursor appears, and flickers, but I am left just staring at the boot log. I dont get a log in screen.
If I log into a terminal and do a 'ps -eaf | grep Xorg' then I can see a xorg process.
My Fedora 17 installation is no longer booting into X : it finished loading the boot screen, then the cursor turns into an "X", flashes a quickly a few times then the just stalls.
To get X to load, I have to log into a terminal, kill the Xorg process and run it manually using "startx", at which point it all works fine.
I thought it might have been an issue with the "plymouth" service, as describ
WonderWoofy wrote:I just masked the things that I don't use. I think that included some kind of plymouth-wait, plymouth, and auditd.Edit: This has nothing to do with your question, but I noticed you have a /tmp partition. Do yu actually need a persistent /tmp? Or did you just do this because it is what you are used to doing? Systemd includes a tmp.mount file that autom
I have made a plymouth splash screen (its simple- it just displays a .png image) consisting of simple.plymouth, simple.script, simple.grub and wallpaper.png. Only, I cannot set it as default y editing the default.plymouth file (that errors) or through
sudo update-alternatives --set default.plymouth /lib/plymouth/themes/MYTHEME/simple.plymouth
it errors back at me saying no setting exists.
Email this page
