[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-12-06 Thread Ray Link
Also note that the previous (current) version of network-manager (1.2.6-0ubuntu0.16.04.1) is also failing s390x autopkgtest. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-30 Thread Ray Link
The autopkgtest failure on s390x is in a test that checks rfkill integration. s390 kernels do not have CONFIG_RFKILL set. Behavior change might have something to do with the recent change to s390x autopkgtest from LXC containers to VMs?

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-29 Thread Ray Link
Version 1.2.6-0ubuntu0.16.04.2 has been deployed here to several machines that were experiencing the bug multiple times per day. All DHCP renewal requests since deployment have resulted in renewal notifications being successfully delivered to NetworkManager. ** Tags removed:

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-27 Thread Ray Link
Sorry for the delay - I was away for a week. I have deployed the packages from -proposed and will confirm after keeping an eye on DHCP lease renewals for a while. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-14 Thread Ray Link
Sjors: I'm interested to know how it goes for you with this update (either from the included debdiff, or from the packages when they hit -proposed.) We were seeing the exact same symptoms you were, and deep-dove into your backported fix from the GNOME bug and it all seems like it should fix the

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-14 Thread Ray Link
** Description changed: I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-08 Thread Ray Link
Correction/Addendum to the SRU justification above: Fixed in current Ubuntu. Bionic uses NM 1.8.x. This bug was fixed in 1.4. [Impact] * This LP bug's original submitter backported the upstream 1.4 fix to 1.2, not Upstream. [Regression Potential] * The patch changes both nm-dhcp-helper and

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-08 Thread Ray Link
[Impact] * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP lease renewal due to a DBus race condition. * Upstream NetworkManager 1.4 fixes the race condition by changing nm-dhcp-helper's DBus notification from signal "Event" to method "Notify". * Upstream

[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

2017-11-08 Thread Ray Link
Upstream GNOME bug fixed. I've applied the fix to Xenial's NM and tested. SRU incoming. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1696415 Title: NetworkManager does

[Desktop-packages] [Bug 1676993] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-03-28 Thread Ray Link
*** This bug is a duplicate of bug 1676380 *** https://bugs.launchpad.net/bugs/1676380 ** This bug has been marked a duplicate of bug 1676380 Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures -- You received this bug notification because you are a member of

[Desktop-packages] [Bug 1676993] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2017-03-28 Thread Ray Link
Can confirm. Saw this failure on dozens of machines today when 2.1.3-4 failed to upgrade to 2.1.3-4ubuntu0.2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1676993 Title: package