Dear all!
I have Ubuntu 16.04 LTS installed.
No special software here. No PPAs. Only MATE desktop with LTSP-server components.
Sometimes my system does not have network after boot:
$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:79 errors:0 dropped:0 overruns:0 frame:0
TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:5335 (5.3 KB) TX bytes:5335 (5.3 KB)
I have already found corresponding bug report 1487679 about break ordering cycle in systemd.
My symptoms are the same as in it:
$ dmesg | grep break
[ 4.634456] systemd[1]: sockets.target: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start
[ 4.634893] systemd[1]: acpid.path: Job acpid.path/start deleted to break ordering cycle starting with paths.target/start
[ 4.635273] systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with NetworkManager-wait-online.service/start
What should I do to force developers to fix this bug? Or to increase its importance?
Asking on AskUbuntu will not help, I think.
27 users are affected (plus 7 and 15 with duplicates - bug 1465196 and bug 1582986 ).
As far I can understand Ubuntu is enterprise-grade operating system, does not it?
It should provide 99.999999% uptime.
With best regards,
Norbert.