On 09/10/14 20:49, Anders Wegge Keller wrote:
Systemd is probably involved, but I rather suspect plymouth to be
the real
culprit. If you have the ability to get to a console (CTRL+ALT+Fn), try
logging in as root there, and switch to runlevel 3 and back to runlevel 5.
That does the trick for me.
You may be on to something.....
I don't have the problem that the OP is having. But I noted that in all my logs, at
boot time I get 2 lines which are similar to...
Sep 03 08:52:45 meimei systemd[1]: Received SIGRTMIN+20 from PID 241 (plymouthd).
and
Sep 03 08:53:13 meimei systemd[1]: Received SIGRTMIN+21 from PID 241 (plymouthd).
Which you can see are about 30 seconds apart. The failure log supplied by the OP had only
one line
set 10 05:59:55 Fujiantonio systemd[1]: Received SIGRTMIN+20 from PID 218 (plymouthd).
--
If you can't laugh at yourself, others will gladly oblige.