On Mon, 28 Jul 2014, Michael Biebl wrote:
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.
Indeed. It is surprising, I did see one earlier, I copy-pasted the message
in google and that's how I eventually found this bug, but now I don't see
it anymore...
I have this in syslog from another boot. Ah, could it be from when I tried
enabling NetworkManager-wait-online.service? I thought I had removed that
as soon as I realized it didn't solve the problem.
Jul 28 12:51:12 stedding systemd[1]: Found ordering cycle on
basic.target/stop
Jul 28 12:51:12 stedding systemd[1]: Found dependency on
sysinit.target/stop
Jul 28 12:51:12 stedding systemd[1]: Found dependency on
nfs-common.service/stop
Jul 28 12:51:12 stedding systemd[1]: Found dependency on
rpcbind.target/stop
Jul 28 12:51:12 stedding systemd[1]: Found dependency on
rpcbind.service/stop
Jul 28 12:51:12 stedding systemd[1]: Found dependency on
network-online.target/stop
Jul 28 12:51:12 stedding systemd[1]: Found dependency on
network.target/stop
Jul 28 12:51:12 stedding systemd[1]: Found dependency on
NetworkManager-wait-online.service/stop
Jul 28 12:51:12 stedding systemd[1]: Found dependency on basic.target/stop
Jul 28 12:51:12 stedding systemd[1]: Breaking ordering cycle by deleting
job sysinit.target/stop
Jul 28 12:51:12 stedding systemd[1]: Job sysinit.target/stop deleted to
break ordering cycle starting with basic.target/stop
So I'm not sure if the issue you're seeing is related to this particular
bug report.
At least the remote_fs -> local_fs change works, though that could be a
coincidence.
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.
If there is no cycle but messing with the order fixes it, that would point
to a missing dependency somewhere I guess?
--
Marc Glisse
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
