<---- template headericclude ----->
Failed to start Wait for Plymouth Boot Screen to Quit
FedoraForum.org - Fedora Support Forums and Community
Page 1 of 2 12 LastLast
Results 1 to 15 of 21
  1. #1
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Failed to start Wait for Plymouth Boot Screen to Quit

    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
    Last edited by broadstairs; 21st September 2013 at 08:13 AM.

  2. #2
    Join Date
    Jul 2012
    Location
    California
    Posts
    9
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    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
    Last edited by drammar; 21st September 2013 at 10:16 AM.

  3. #3
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    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

  4. #4
    Join Date
    Jul 2013
    Location
    Lviv, Ukraine
    Posts
    4
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

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

  5. #5
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    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

  6. #6
    Join Date
    Feb 2006
    Location
    Modbury, Australia
    Posts
    99
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    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 ...

  7. #7
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

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

    Stuart

  8. #8
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    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

  9. #9
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    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

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

  10. #10
    Join Date
    Jul 2013
    Location
    Lviv, Ukraine
    Posts
    4
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    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

  11. #11
    Join Date
    Jan 2006
    Posts
    237
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    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.

  12. #12
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    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

  13. #13
    Join Date
    Jan 2006
    Posts
    237
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

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

  14. #14
    Join Date
    Oct 2011
    Location
    UK
    Posts
    469
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    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

  15. #15
    Join Date
    Oct 2013
    Location
    Texas
    Posts
    15
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Failed to start Wait for Plymouth Boot Screen to Quit

    Seems to be working for me as well

Page 1 of 2 12 LastLast

Similar Threads

  1. [SOLVED]
    Failed to start Wait for Plymouth Boot Screen to Quit
    By jonnycat in forum Using Fedora
    Replies: 2
    Last Post: 20th September 2013, 07:47 AM
  2. [SOLVED]
    F17 failed to start, wait for plymouth boot screen to quit
    By taytong888 in forum Using Fedora
    Replies: 2
    Last Post: 5th February 2013, 01:58 AM
  3. Replies: 8
    Last Post: 16th December 2012, 09:00 PM
  4. Replies: 0
    Last Post: 29th November 2011, 12:12 AM
  5. Starting Wait for Plymouth Boot Screen to quit
    By demetris in forum Using Fedora
    Replies: 9
    Last Post: 19th October 2011, 07:09 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
[[template footer(Guest)]]