On Tue 02 Aug 2016 at 17:08:28 +0100, Brian Potkin wrote: > On Thu 16 Jun 2016 at 18:33:45 +0200, Kristian Klausen wrote: > > > I just checked NetworkManager, and they only install it > > (NetworkManager-wait-online.service) but does not enable it. > > > > I think that is the correct behavior, next time someone update connman > > they could fix this bug :) > > Please see #812209, Message #25. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812209 > > While we still have a few stragglers left, the most important blockers > have been dealt with. So I enable NM-wait-online with the last upload.
Having said that, there is still the question of the issue reported by Florian; I see behaviour which supports his observations. 'apt-get install connman' sees the install process get to creating symlinks and then hanging for nearly 2.5 minutes. This is very, very disconcerting. I have not experienced anything like this before. Eventually, it completes with the message: connman-wait-online.service couldn't start. Sure enough, systemctl shows the unit in a failed state. I nearly forgot to mention: that was with no ethernet cable connected and the package cached. Connecting the cable and installing connman takes the usual few seconds and connman-wait-online.service is active afterwards. Regards, Brian.
