network-manager - kubuntu 16.04, unable to change existing network interface : reason="connection.gateway-ping-timeout: can not set property: value "34163392" of type 'guint' is invalid or out of range for property 'gateway-ping-timeout' of type 'guint'"

Bug #1578533 reported by yossarian_uk
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned
networkmanager-qt (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I am unable to change any settings within network-manager for any wired interface (not tried wireless) - if you try to change anything (i.e dns servers, ipv6 settings, change from dhcp -> dhcp address only) you get an error (and the setting doesn't change)

i.e - in this example I selected 'require IPV4' and I get

May 5 09:13:08 mcox-N552VW NetworkManager[810]: <info> [1462435988.7023] audit: op="connection-update" uuid="c91931f0-15d1-4d29-9b76-e80ef5a4abcd" name="Wired connection 1" result="fail" reason="connection.gateway-ping-timeout: can not set property: value "34184640" of type 'guint' is invalid or out of range for property 'gateway-ping-timeout' of type 'guint'"

(similar errors occur if you try to change any setting)

This is happening on multiple machines.

As a 'work-around' you have to remove the interface and re-add to change settings.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Thu May 5 09:04:39 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-05-03 (1 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.90.1 dev enp3s0f1 proto static metric 100
 default via 192.168.90.1 dev wlp2s0 proto static metric 600
 169.254.0.0/16 dev enp3s0f1 scope link metric 1000
 192.168.90.0/24 dev enp3s0f1 proto kernel scope link src 192.168.90.187 metric 100
 192.168.90.0/24 dev wlp2s0 proto kernel scope link src 192.168.90.147 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 enp3s0f1 ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 c91931f0-15d1-4d29-9b76-e80ef5a4abcd /org/freedesktop/NetworkManager/ActiveConnection/0
 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 CPGB-STAFF 07b9076e-a493-4bdf-bf85-0c77537cc692 /org/freedesktop/NetworkManager/ActiveConnection/1
 B8:5E:7B:22:5B:F0 bt disconnected /org/freedesktop/NetworkManager/Devices/3 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Revision history for this message
yossarian_uk (morgancoxuk) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Portnov (portnov84) wrote :

Hi
Any updates please? This is pretty serious bug; host is unable to connect to network after system startup. sudo service network-manager restart helps, but it is not convenient to restart service manually after system startup...

Revision history for this message
yossarian_uk (morgancoxuk) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in networkmanager-qt (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.