Updated bionic to the current 1.10 stable version

[Sebastien Bacher]

* Impact

The updates in the stable serie include several fixes for misbehaviour, segfaults and security issues, those are the sort of improvements that should be in the LTS

The detail of the changes can be seen in the NEWS entry
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS

* Test case

There is no specific test case for the update, the changelog includes some specific bugs which have their own test case, otherwise it's important to get testing/feedback from users on desktop & server, using IPv4, IPv6, VPN, wifi, eth connections, etc.

* Regression potential

The update is non trivial, there are several changes are IPv6 and DNS (especially in the context of VPNs) handling so it would be good to give those extra testing

[Launchpad Janitor (janitor)]

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

[Brian Murray (brian-murray)]

Hello Sebastien, or anyone else affected,

Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network-manager/1.10.14-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Olivier Tilloy (osomon)]

Please test and share your feedback on this new version here, but refrain from changing the verification-needed-bionic tag for now. This new version includes many changes and we want to give it an extended testing period to ensure no regressions sneak in, before it is published to bionic-updates. Thanks!

[Gijs Molenaar (gijzelaar)]

I've installed and been running 1.10.14-0ubuntu1 for a while without problems now.

[Eric Desrochers (slashd)]

Hi osomon,

Do we have enough testing to consider a copy into bionic-updates soon ?
I haven't dig but I saw a few ADT regressions in pending sru page.
Are they a blocker ? or known failures ?

[Till Kamppeter (till-kamppeter)]

I have set up Bionic on an old laptop now and updated it with -proposed included, landing on network-manager 1.10.

I have done some tests:

- Connection via Wi-Fi works (also switching to a second WLAN and when the second WLAN goes away it automatically returns to the first),
- Connection with a USB modem which appears as USB Ethernet adapter works
- Setting up and accessing the Canonical internal VPN works.
- Getting into the internet connecting to a Google Pixel 2 via Bluetooth does not work (but this also does not work with Disco).
- No crashes since the machine is running.
- Internet access works normally, without any issues.

[Till Kamppeter (till-kamppeter)]

Sorry, I mean network-manager 1.10.14.

[Till Kamppeter (till-kamppeter)]

Now my Bionic test box is running for the whole weekend and it does not show any irregularities. No crash reports. The new network-manager seems to work fine on Bionic.

[Till Kamppeter (till-kamppeter)]

Also on the Bionic VM on my main laptop I have updated network-manager to 1.10.14 and there are no issues.

[Till Kamppeter (till-kamppeter)]

Now after 3 months time for testing and no complaints coming up, Ken VanDine, Will Cooke, Olivier Tilloy, and me agreed on considering this SRU as verified. So I have marked this bug report appropriately.

Thanks to everyone who has tested this.

[Timo Aaltonen (tjaalton)]

Hello Sebastien, or anyone else affected,

Accepted network-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network-manager/1.10.14-0ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Till Kamppeter (till-kamppeter)]

Resetting verification status to verification-done as the re-upload is a trivial fix of the autopkg test which does not change anything in the functionality of the package itself.

[Launchpad Janitor (janitor)]

This bug was fixed in the package network-manager - 1.10.14-0ubuntu2

---------------
network-manager (1.10.14-0ubuntu2) bionic; urgency=medium

  [ Till Kamppeter ]
  * debian/tests/nm: Add gi.require_version() calls for NetworkManager
    and NMClient to avoid stderr output which fails the test.

  [ Iain Lane ]
  * debian/tests/control: The nm tests need dnsmasq-base and isc-dhcp-client
    too.

network-manager (1.10.14-0ubuntu1) bionic; urgency=medium

  * New stable version (LP: #1809132), including:
    - Support private keys encrypted with AES-{192,256}-CBC in libnm
      (LP: #942856)
    - Fix leak of DNS queries to local name servers when connecting to a
      full-tunnel VPN (CVE-2018-1000135) (LP: #1754671)
  * Dropped patch applied upstream:
    - debian/patches/CVE-2018-15688.patch
    - debian/patches/e91f1a7d2a6b8400b6b331d5b72287dcb5164a39.patch
  * Refreshed patches:
    - debian/patches/Don-t-make-NetworkManager-D-Bus-activatable.patch
    - debian/patches/Force-online-state-with-unmanaged-devices.patch
    - debian/patches/Read-system-connections-from-run.patch
    - debian/patches/Update-dnsmasq-parameters.patch
    - debian/patches/libnm-register-empty-NMClient-and-NetworkManager-when-loa.patch

 -- Till Kamppeter <email address hidden> Fri, 10 May 2019 13:34:00 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for network-manager has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Steve Langasek (vorlon)]

Due to the SRU regressions reported in LP: #1829838 and LP: #1829566, I have reverted this SRU for the moment, restoring network-manager 1.10.6-2ubuntu1.1 to bionic-updates. I am marking this bug verification-failed pending resolution of the reported regressions.

[Sebastien Bacher (seb128)]

SRUing the newer version failed since it changed behaviour in some configuration which created issue for existing users.

There isn't anyone currently working on resolving those issues so it's more realistic to untarget from Bionic.

If the problem really needs to be resolved in that serie best to go through the rls-bb-incoming nomination process again.