Am 28.07.2014 17:23, schrieb Marc Glisse: >> The output of "systemctl list-jobs" and "journalctl -alb" would be >> helpful for a start. > > The first only listed: > 497 systemd-logind.service start running > > The second is: > http://geometrica.saclay.inria.fr/team/Marc.Glisse/tmp/systemd > > It seems that the NetworkManager service is the only one really failing, > maybe because of policykit. > (you can probably ignore the ldap messages, they have always been there) > I ran "/etc/init.d/gdm3 stop" before so it wouldn't try to switch tty > everytime an attempt to start X failed.
I don't see a dependency cycle in the journal output you posted. So I'm not sure if the issue you're seeing is related to this particular bug report. What I see is quite a few of Jul 28 16:38:25 stedding dbus[652]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out Jul 28 16:38:25 stedding dbus[652]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out Jul 28 16:38:25 stedding dbus[652]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out Which then leads to PolicyKit and as a consequence NM being non-functional. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
