This bug was fixed in the package network-manager - 1.2.2-0ubuntu4
---------------
network-manager (1.2.2-0ubuntu4) yakkety; urgency=medium
[ Mathieu Trudel-Lapierre ]
* debian/patches/libnm-Check-self-still-NMManager-or-not.patch: updated and
refreshed to make gbp pq happy.
* debian/patches/Read-config-from-run.patch: also read configuration from
/run, which is to override whatever might be shipped in /usr/lib; and be
overriden by /etc or command-line arguments. (LP: #1591898)
* debian/10-globally-managed-devices.conf: ship a default config to
explicitly unmanage anything that is not wifi or wwan: we definitely want
NM to manage wifi and mobile data; and probably don't want it to touch
wired in many cases.
* debian/network-manager.postinst: on upgrade from previous versions of NM,
make sure we migrate from no global "unmanaged" policy to something
equivalent where we may have a global policy, but explicitly override it
to be disabled; so that on upgrade users do not suddenly see some of their
network devices no longer being handled by NM.
* debian/patches/dns-manager-don-t-merge-split-DNS-search-domains.patch: do
not add split DNS search domains to resolv.conf; doing so would risk
leaking names to non-VPN DNS nameservers when attempting to resolve non-
FQDN names. (LP: #1592721)
[ Martin Pitt ]
* debian/NetworkManager.conf: Put back dns=dnsmasq for now. Some important
applications such as Chrome don't use NSS but reimplement DNS resolution,
for those we need a local DNS server. Until resolved gets one, we continue
to use the NM specific dnsmasq on the desktop. Correspondingly, revert
libnss-resolve recommends back to dnsmasq-base depends.
-- Mathieu Trudel-Lapierre <cypher...@ubuntu.com> Thu, 16 Jun 2016
09:54:02 +0300
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1591898
Title:
NetworkManager should parse system config from /run/NetworkManager
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
NetworkManager currently only reads configuration files from
/etc/NetworkManager/NetworkManager.conf and
/etc/NetworkManager/conf.d.
It should be possible to also read and write config from
/run/NetworkManager/conf.d; so that any changes to the system
configuration done by NM would land in /run, rather than modifying
/etc/ (which is meant only to be changed by the system owner). This
would also allow other system tools to add configuration for
NetworkManager to use, that might be dynamically written.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1591898/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
