That was discussed on IRC and there are some details in the upstream report (https://bugzilla.gnome.org/show_bug.cgi?id=779776)
The main issue on the GNOME side seems to be that libnm and libnm-glib bindings can't be loaded at the same time, which means that gnome-shell and its plugins need to be using the same library, which means they need to be updated in sync to avoid issue. There doesn't seem to be a need to remove libnm-glib from Ubuntu yet though (if it's still needed/used), upstream hasn't removed it either but building the nm plugins without it might lead to issues for unity- control-center which is using the old library still ** Bug watch added: GNOME Bug Tracker #779776 https://bugzilla.gnome.org/show_bug.cgi?id=779776 ** Summary changed: - libnm-glib removal transition + Transitioning GNOME away from libnm-glib -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744619 Title: Transitioning GNOME away from libnm-glib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-iodine/+bug/1744619/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
