systemctl service NetworkManager reports GLib errors in status

[Thilo Cestonaro]

Ubuntu Wily (packages updated today latest):

Visual:
nm-applet is not showing up
network not configured

background:
sudo systemctl status network-manager -l

● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Mo 2015-09-21 14:07:47 CEST; 18s ago
 Main PID: 5605 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           └─5605 /usr/sbin/NetworkManager --no-daemon

Sep 21 14:07:47 myhost NetworkManager[5605]: <info> devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Sep 21 14:07:47 myhost NetworkManager[5605]: <info> device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Sep 21 14:07:47 myhost NetworkManager[5605]: <info> end _init.
Sep 21 14:07:47 myhost NetworkManager[5605]: <info> Loaded settings plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-settings-plugin-ifupdown.so)
Sep 21 14:07:47 myhost NetworkManager[5605]: <info> Loaded settings plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): GLib-GObject-WARNING **: cannot register existing type 'NMSetting'
Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed
Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed
Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): libnm-util-CRITICAL **: _nm_register_setting: assertion 'type != G_TYPE_INVALID' failed
Sep 21 14:07:47 myhost NetworkManager[5605]: (NetworkManager:5605): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

[Thilo Cestonaro (tephraim)]

Another thing is:
dbus-send --system --type=method_call --print-reply --dest=org.freedesktop.NetworkManager / org.freedesktop.DBus.Introspectable.Introspect

Returns with the following error:
Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Usually this should be something like this:
dbus-send --system --type=method_call --print-reply --dest=org.freedesktop.ModemManager1 / org.freedesktop.DBus.Introspectable.Introspect

method return time=1442906750.384191 sender=:1.4 -> destination=:1.140 serial=74 reply_serial=2
   string "<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
                      "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
<!-- GDBus 2.45.7 -->
<node>
  <node name="org"/>
</node>
"

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Thilo Cestonaro (tephraim)]

Seems to be fixed with network-manager 1.0.4-0ubuntu4. DBus works again and systemctl status doesn't show the assertions anymore.

Thanks!