This bug was fixed in the package network-manager - 1.12.4-1ubuntu1
---
network-manager (1.12.4-1ubuntu1) cosmic; urgency=medium
* Merge with Debian (LP: #1795704). Remaining changes:
- Use systemd-resolved instead of dnsmasq
- debian/control:
+ Depend on isc-dhcp-client instead of recommends
+ Recommend network-manager-pptp
+ Suggest avahi-autoipd for IPv4LL support
- debian/rules, debian/network-manager.postinst:
+ Don't restart NetworkManager on upgrade but recommend restarting
the computer
- debian/rules, debian/network-manager.postinst:
+ Don't install sysvinit scripts or migrate from sysvinit
- debian/network-manager.postinst:
+ Don't add the netdev group.
+ drop in an empty override file for NetworkManager to manage all
devices for upgrade from any version, as long as there is no
netplan configuration yet.
- debian/network-manager.maintscript
+ Remove /etc/dbus-1/system.d/nm-ofono.conf
- debian/default-wifi-powersave-on.conf, debian/rules:
+ Install a config file to enable WiFi powersave
- Enable build tests
- Add autopkgtests
- debian/source_network-manager.py, debian/network-manager.install,
debian/network-manager.links: Add apport hook
- Add network-manager-config-connectivity-ubuntu package
- NetworkManager.conf: disable MAC randomization feature. There is no
easy way for desktop users to disable this feature yet. And there are
reports that it doesn't work well with some systems.
- Update Vcs links to point to Ubuntu branch
- Add patches. See patch descriptions for more details:
+ Provide-access-to-some-of-NM-s-interfaces-to-whoopsie.patch
+ Update-dnsmasq-parameters.patch
+ Disable-general-with-expect.patch
+ libnm-Check-self-still-NMManager-or-not.patch
+ dns-manager-don-t-merge-split-DNS-search-domains.patch (but disabled)
+ Read-system-connections-from-run.patch
- debian/tests/urfkill-integration - don't stop/start network manager
* Revert "Add Conflicts to network-manager-dev against deprecated libraries"
This reverts commit b4acc5e03e2b821e169529bb70826c741942. We're still
building libnm-glib for now, so these packages have a use in Ubuntu.
network-manager (1.12.4-1) unstable; urgency=medium
* New upstream version 1.12.4
* Rebase patches
network-manager (1.12.2-3) unstable; urgency=medium
[ Simon McVittie ]
* Apply patch from upstream to fix FTBFS with GLib 2.57 (Closes: #906965)
network-manager (1.12.2-2) unstable; urgency=medium
* Fix compile error due to NM_AVAILABLE_IN_1_12_2 macro (Closes:
#905372)
network-manager (1.12.2-1) unstable; urgency=medium
* New upstream version 1.12.2
- Robustness fixes to connectivity checking (Closes: #903996)
* Rebase patches
* Update symbols file for libnm0
* Bump Standards-Version to 4.1.5
-- Iain Lane Wed, 03 Oct 2018 10:03:10 +0100
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => 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/1795704
Title:
Update to 1.12.4
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
We should merge this
===
NetworkManager-1.12.4
Overview of changes since NetworkManager-1.12.2
===
This is a new stable release of NetworkManager. Notable changes
include:
* Fix reapplying different route-metric for automatic routes.
* Fix crash in connectivity check.
* Fix accepted input format for vpn.secrets in nmcli's password file.
* libnm: support private keys encrypted with AES-{192,256}-CBC.
* Fix stopping pppd on modem hangup
* Various minor bugfixes and translation updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1795704/+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
