This happens only sometimes on my system. In most of cases NetworkManager starts normally but dnscrypt-proxy fails. It happens on two installations. $ sudo journalctl | grep network июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found ordering cycle on network.target/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on NetworkManager.service/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on dbus.service/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on basic.target/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on sockets.target/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on dnscrypt-proxy.socket/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Found dependency on network.target/start июл 26 11:53:24 sunsetshimmer systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start июл 26 11:53:24 sunsetshimmer systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start июл 26 11:53:26 sunsetshimmer systemd[1]: Started Trigger resolvconf update for networkd DNS. июл 26 11:53:26 sunsetshimmer systemd[1]: Starting Raise network interfaces... июл 26 11:53:26 sunsetshimmer systemd[1]: Started Raise network interfaces. июл 26 11:53:26 sunsetshimmer systemd[1]: Starting Anonymizing overlay network for TCP (multi-instance-master)... июл 26 11:53:26 sunsetshimmer systemd[1]: Starting Anonymizing overlay network for TCP... июл 26 11:53:26 sunsetshimmer systemd[1]: Starting load-balanced unspoofable packet switching network... июл 26 11:53:26 sunsetshimmer systemd[1]: Started Anonymizing overlay network for TCP (multi-instance-master). июл 26 11:53:27 sunsetshimmer systemd[1]: Started load-balanced unspoofable packet switching network. июл 26 11:53:27 sunsetshimmer systemd[1]: Started Anonymizing overlay network for TCP.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1582986 Title: NetworkManager service does not start during bootup Status in network-manager package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 4.4.0-22 systemd 229-4 network-manager 1.1.93 network-manager-gnome 1.2.0 Multiple services and targets are deleted by systemd to "break ordering cycle" (cf. boot.log), but NetworkManager is the only one of them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote- fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective logs) which is not started after bootup: sudo systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: inactive (dead) May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job NetworkManager.service/verify-active deleted to break ordering cycle starting with network.target/start Attachments: ----------- - journalctl -l -b0 --system _COMM=systemd > boot.log - systemctl -l status rpcbind > rpcbind.log - systemctl -l status network.target > network.target.txt - systemctl -l status remote-fs-pre.target > remote-fs-pre.target.log - systemctl -l status sysinit.target > sysinit.target.log - systemctl -l status zfs-fuse.service > zfs-fuse.service.log - systemctl -l status open-iscsi.service > open-iscsi.service.log - systemctl -l status iscsid.service > iscsid.service.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
