© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Hi Ray/Julian,
> * NOTE: The final comment on the upstream GNOME bug claims that the fix
> is incomplete. However, it is possible that the running NetworkManager was
> not restarted (see Regression Potential notes above), which is why
> nm-dhcp-helper is falling back to Event.
This is not the case. Even today, one of the machines is showing the message from the wrapper that indicates the DHCP lease was not correctly applied according to the journal:
➜ sjors@cuba ~ cat /tmp/nm-
Tue Nov 14 07:23:07 CET 2017: needed 5 attempts to update NetworkManager (RENEW).
Tue Nov 14 09:17:45 CET 2017: needed 5 attempts to update NetworkManager (RENEW).
Tue Nov 14 10:06:58 CET 2017: needed 4 attempts to update NetworkManager (RENEW).
This is even though the machine was rebooted yesterday, so the daemon was restarted:
➜ sjors@cuba ~ uptime
23:12:16 up 1 day, 14:04, 3 users, load average: 0,59, 0,49, 0,47
And the machine is using the patched version of the network-manager:
➜ sjors@cuba ~ apt-cache policy network-manager
network-manager:
Installed: 1.2.6-0ubuntu0.
Candidate: 1.2.6-0ubuntu0.
Version table:
*** 1.2.6-0ubuntu0.
100 /var/lib/
1.
500 http://
However, I have not investigated why this happens, as the wrapper script is an acceptable work-around. I'll report back, however, whether we still have this problem with the updated Xenial packages -- there is always a chance I made an error somewhere.