Failed to start Wait for Plymouth Boot Screen to Quit

**broadstairs** · 21st September 2013, 08:08 AM

I have this happening now on the latest update and I have seen this thread being referred to as the issue. However I do not have an Nvidia gfx card but and ATI one, also I do not use the catalyst driver.

I can get a terminal screen, login and startx OK and this is how I am posting this.

Is there something else which is causing my problem?

Stuart

**drammar** · 21st September 2013, 10:11 AM

That's not the only issue.

If you have a NVIDIA video card, it's not the Plymouth Boot Screen that is hanging you. I also saw that failure but it went right past it. What is hanging you are video drivers.

With this kernel, the drivers in xorg-x11-drv-nvidia-304xx will not work. In fact looking at the log files of X windows starting, it cannot find the nvidia module. The simple fix... reboot and load a prior kernel. I am sure that this package will be updated soon for the new kernel.

I do not know if ATI or Intel cards are affected.

---------- Post added at 02:11 AM ---------- Previous post was at 02:10 AM ----------

Kernel version that triggers the issue: 3.11.1
Driver package: xorg-x11-drv-nvidia-304xx-304.88-12.fc19.x86_64

**broadstairs** · 21st September 2013, 10:16 AM

I dont have an NVIDIA card and I dont have any of the akmod stuff installed or any of the NVIDIA drivers installed at all so they have always been not there. I tried booting the level 10 kernel and get the same problem. (I dont have any older kernels now to try).

Obviously my problem then is something different so I would appreciate some help in where to look or what to, look for?

Stuart

**Arch3r** · 21st September 2013, 10:36 AM

Take a look to linuxquestions forum. Maybe this will help you to solve a problem

**broadstairs** · 21st September 2013, 11:54 AM

Well I am really confused as I followed a tip there to rename the /var/log/journal to /var/log/journal.org and now my system boots just fine. How the h*ll would anyone know to do that? I'll wait to see if the problem has gone away completely for a day or so before I mark as solved.

Stuart

**ausadl** · 21st September 2013, 12:47 PM

I have same problem as broadstairs. I do have NVIDIA card but no kmod, akmod involved. I had to stay with kernel-3.9.5-301.fc19.x86_64. Every kernel after that is a trouble ...

**broadstairs** · 21st September 2013, 05:02 PM

Well I've just come in and booted my system and no sign of this message on this boot at all.

Stuart

**broadstairs** · 26th September 2013, 08:09 AM

Well this problem just happened again and now I have /var/log/journal.org directory and /var/log/journal which has been updated. So this rename simply seems to remove the standard directory so the system creates a new one. So the so-called fix may not really be any more than a bypass. Still cannot find anything which looks like it should cause this problem.

Anyone any new ideas please?

Stuart

**broadstairs** · 27th September 2013, 08:40 AM

Well having sorted some other errors like the NetworkManager-dispatcher.service not running I am still seeing this problem. The last part of my boot log shows

[[32m OK [0m] Started LSB: VirtualBox autostart service.
[[32m OK [0m] Started LSB: VirtualBox web service API.
[[32m OK [0m] Started LSB: VirtualBox balloon control daemon.
[[32m OK [0m] Started Network Manager Script Dispatcher Service.
[[32m OK [0m] Started RealtimeKit Scheduling Policy Service.
[[32m OK [0m] Started Login Service.
[[0m[31m* [0m] (1 of 7) A start job is running for Avahi mDNS/DNS-SD Stack
[K[[1;31m*[0m[31m* [0m] (1 of 7) A start job is running for Avahi mDNS/DNS-SD Stack
[K[[31m*[1;31m*[0m[31m* [0m] (1 of 7) A start job is running for Avahi mDNS/DNS-SD Stack
[K[ [31m*[1;31m*[0m[31m* [0m] (2 of 7) A start job is running for NTP client/server
[K[ [31m*[1;31m*[0m[31m* [0m] (2 of 7) A start job is running for NTP client/server
[K[ [31m*[1;31m*[0m[31m*[0m] (2 of 7) A start job is running for NTP client/server
[K[ [31m*[1;31m*[0m] (3 of 7) A start job is running for Network Manager
[K[ [31m*[0m] (3 of 7) A start job is running for Network Manager
[K[ [31m*[1;31m*[0m] (3 of 7) A start job is running for Network Manager
[K[ [31m*[1;31m*[0m[31m*[0m] (4 of 7) A start job is running for Wait for Plymouth Boot Screen to Quit
[K[ [31m*[1;31m*[0m[31m* [0m] (4 of 7) A start job is running for Wait for Plymouth Boot Screen to Quit
[K[[1;31mFAILED[0m] Failed to start Wait for Plymouth Boot Screen to Quit.
See 'systemctl status plymouth-quit-wait.service' for details.
[[32m OK [0m] Started LSB: DKMS kernel modules installer service.
[ [31m*[1;31m*[0m[31m* [0m] (4 of 5) A start job is running for LSB: TurboPrint usb port daemon
[K[[31m*[1;31m*[0m[31m* [0m] (5 of 5) A start job is running for Accounts Service
[K[[32m OK [0m] Started NTP client/server.
Starting Authorization Manager...

My Xorg.0.log shows no errors at all but that I guess is only recorded after I login via a terminal screen and issue startx.

The only thing in messages log I dont understand is

dbus-daemon[557]: dbus[557]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.nm-dispatcher.service' for details.
Sep 27 07:37:31 F19Main dbus[557]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.nm-dispatcher.service' for details.
Sep 27 07:37:31 F19Main NetworkManager[524]: <warn> Dispatcher failed: (32) Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.nm-dispatcher.service' for details.

I'm hoping someone will come up witha solution to this problem. As I said before it disappeared after renaming the journal directory in /var/log but the journal directory comes back again and so does this problem.

Stuart

**Arch3r** · 27th September 2013, 09:41 AM

There is a bug about this error messages in /var/log/messages:
https://bugzilla.redhat.com/show_bug.cgi?id=974811
so, probably, you have to wait for a fix in NetworkManager package

**Krister Hallerg** · 27th September 2013, 11:50 AM

Have the same problem as broadstairs. I used Catalyst, but got problems to start the graphical interface after a recent kernel update, so I uninstalled Catalyst. But later, after further updates I got this problem instead. I have concluded that the update of KDE to 4.11.1 si the cause. It seems to me that kdm is not succeeding in qetting Plymouth to quit.

Anyway, I followed your tip to rename the folder /var/log/journal/99938573c9d70e2f98229769926fbd74 and after that I have managed two reboots without this problem.

**broadstairs** · 27th September 2013, 01:47 PM

Well I renamed the journal directory again and now have booted OK. Also at this time the journal directory has NOT been recreated. There are a number of differences in what is happening at boot time when comparing the failed and working logins, I cant help feeling the the journal has something to do with it.

Anyone any ideas?

Stuart

**Krister Hallerg** · 28th September 2013, 06:14 AM

Also my third boot successful. Folder /var/log/journal/99938573c9d70e2f98229769926fbd74 has been recreated and has two files: system.journal and user-1000.journal

**broadstairs** · 29th September 2013, 06:03 PM

Been a couple of days now and each boot has worked, so far the /var/log/journal directory has NOT been recreated. It will be interesting to see if the problem comes back as soon as this directory gets re-created.

Stuart

**mwoolweaver** · 27th October 2013, 07:46 PM

Seems to be working for me as well

Failed to start Wait for Plymouth Boot Screen to Quit

Thread Tools

Search Thread

Display