[Pkg-utopia-maintainers] Bug#813803: Bug#813803: network-manager: Network-manager update to 1.1.90-4 in unstable broken if resolvconf enabled

[Giacomo Mulas]

On Fri, 5 Feb 2016, Michael Biebl wrote:

> Sorry for the inconvenience. I actually remember (open)resolvconf
> related problems and talked to upstream about that.
>
> Could you test the following upstream commit:
>
> http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=af189b3295847cf48bc7616ec3bfc4192458608c
>
>
> If that works, I'll upload a new version including that patch.

Apparently yes. I applied that patch on top of the network-manager debian
source package, I recompiled everything in the src directory, hand installed
the resulting NetworkManager executable, and it does not segfault anymore.
I still get, in the debug dump, the following:

NetworkManager[26333]: <debug> [1454681100.518100] [dns-manager/nm-dns-manager.c
:808] update_dns(): dns-mgr: update-dns: updating resolv.conf
NetworkManager[26333]: <info>  dns-mgr: Writing DNS information to /sbin/resolvc
onf
Failed to try-restart named.service: Unit named.service failed to load: No such 
file or directory.
Failed to try-restart unbound.service: Unit unbound.service failed to load: No s
uch file or directory.
NetworkManager[26333]: <warn>  dns-mgr: resolvconf failed with status 3072
NetworkManager[26333]: <debug> [1454681100.577095] [dns-manager/nm-dns-manager.c
:549] update_resolv_conf(): dns-mgr: not updating /var/run/NetworkManager/resolv
.conf since it points to /etc/resolv.conf
NetworkManager[26333]: <warn>  dns-mgr: could not commit DNS changes: resolvconf
  failed with status 3072

However, this is now followed by

NetworkManager[26333]: <info>  (wlan0): Activation: successful, device activated

and everything works again. Actually, /etc/resolv.conf, when I open it,
appears correct, as set up by resolvconf in the openresolv package. Perhaps
that is handled by the /etc/network/if-up.d/000resolvconf hook.

By the way, is it Network-Manager or resolvconf that tries to restart
named.service and unbound.service?  In my laptop it can restart
bind9.service, but there is no named.service.  Indeed, when I look at
/var/log/syslog, I see that named from the bind9 service is indeed reloaded,
I guess that happens due to the /etc/network/if-up.d/bind9 hook whenever an 
interface is brought up.

So, finally, apparently openresolv already does the right things whenever an
interface is brought up or down, so NetworkManager should just leave it
alone and all should work?

Bye
Giacomo

-- 
_________________________________________________________________

Giacomo Mulas <gmulas at oa-cagliari.inaf.it>
_________________________________________________________________

INAF - Osservatorio Astronomico di Cagliari
via della scienza 5 - 09047 Selargius (CA)

tel.   +39 070 71180244
mob. : +39 329  6603810
_________________________________________________________________

"When the storms are raging around you, stay right where you are"
                          (Freddy Mercury)
_________________________________________________________________