You are not logged in.
So I just updated my system and on reboot I can see following output from systemd:
Failed to start Wait for Plymouth Boot Screen to Quit.
See 'systemctl status plymouth-quit-wait.service' for details.
Here is "systemctl status plymouth-quit-wait.service" output:
plymouth-quit-wait.service - Wait for Plymouth Boot Screen to Quit
Loaded: loaded (/usr/lib/systemd/system/plymouth-quit-wait.service; static)
Active: failed (Result: timeout) since Tue, 2012-12-18 12:17:37 FET; 1h 23min ago
Main PID: 1163
CGroup: name=systemd:/system/plymouth-quit-wait.service
GDM can't start. gdm-plymouth.service is enabled. gdm.service is disabled.
Any advice?
Thanks.
Offline
Ah hah! I'm glad I'm not the only one who was having problems. I just did a
systemctl mask plymouth-start
in a different TTY to fix it, but of course that means I have no splash. I'm still looking into it.
The boatcake is coming for you…
Offline
Ah hah! I'm glad I'm not the only one who was having problems. I just did a
systemctl mask plymouth-start
in a different TTY to fix it, but of course that means I have no splash. I'm still looking into it.
Thanks It works, now I can at least access my xmonad
Looking for proper solution.
Offline
Just wanted to add a "me too" to this thread. I'm also still looking for a solution, will check back here regularly, but of course, no splash in the meantime (minor annoyance). I ALSO have an issue with what appears to be plymouthd using up plenty of cycles even though it's "failed" 0_o (I'm using kdm/kde4 btw):
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
372 root 20 0 175m 14m 4408 S 18.7 0.4 5:34.25 @usr/sbin/plymouthd --mode=boot --pid-file=/run/plymouth.pid --attach-to-session
Offline
Guys, do you have issue with plymouth on reboot? I do.
Offline
I had the same problem. In my case it was an issue with Nouveau. I ended up removing Plymouth and switching from Nouveau back to the Nvidia driver (since Plymouth/KMS was my main reason to use Nouveau in the first place). I really appreciate both projects, but they're just a little bit too bleeding-edge for me right now.
Offline
Well, that can't be my problem, since I'm on an Intel graphics, and even my optimus card is using the NVIDIA drivers.
The boatcake is coming for you…
Offline
Worst since I installed mkinitcpio 0.12.0-2
Offline
I'm on bumblebee-nvidia drivers. Maybe mkinitcpio downgrade should help.
Offline
I'm using Intel drivers, btw. I'll probably just end up removing plymouth at this point, since it hasn't worked itself out. Not sure if it's related, but I'm ALSO booting from an encrypted root, and so have the part added to allow typing encryption password at boot. In any case, plymouth is doing nothing on my system at the moment other than having a proc running after bootup that is eating CPU cycles for no apparent reason.
Will continue to follow this thread, however.
Offline
I was able to fix this by copying the missing parameters from gdm.service into gdm-plymouth.service and it works without any issues, I'm not sure if all service parameters are necessary I think the additional After/Conflicts conditions is what actually makes it work.
cat /usr/lib/systemd/system/gdm-plymouth.service
[Unit]
Description=GNOME Display Manager
After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service
Conflicts=plymouth-quit.service getty@tty1.service
#After=plymouth-quit.service
[Service]
ExecStart=/usr/sbin/gdm -nodaemon
StandardOutput=syslog
Restart=always
IgnoreSIGPIPE=no
BusName=org.gnome.DisplayManager
[Install]
Alias=display-manager.service
Offline
I have the exact same problem, is there no fix yet? I tried using the gdm-plymouth.service as described here, but it doesn't work. It's the plymouth-quit-wait.service that fails.
Offline