NetworkManager crash when connecting to openvpn server

Bug #1450985 reported by Oscar Tiderman
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Trying to connect to VPN tunnel but everytime NetworkManager crashes:

May 2 08:49:48 hibbert NetworkManager[19055]: <error> [1430549388.372404] [platform/nm-linux-platform.c:2250] link_change(): Netlink error changing link 9: <DOWN> mtu 0 (1) driver 'unknown' udi '/sys/devices/virtual/net/tun0': No such device
May 2 08:49:48 hibbert NetworkManager[19055]: nm_device_get_priority: assertion 'NM_IS_DEVICE (dev)' failed
May 2 08:49:48 hibbert NetworkManager[19055]: (NetworkManager:19055): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed
May 2 08:49:48 hibbert kernel: [48747.430104] NetworkManager[19055]: segfault at 28 ip 0000000000477817 sp 00007ffd2a3a6c70 error 4 in NetworkManager[400000+10b000]
May 2 08:49:48 hibbert nm-openvpn[19584]: SIGTERM[hard,] received, process exiting
May 2 08:49:50 hibbert systemd[1]: NetworkManager.service: main process exited, code=dumped, status=11/SEGV
May 2 08:49:50 hibbert systemd[1]: Unit NetworkManager.service entered failed state.
May 2 08:49:50 hibbert systemd[1]: NetworkManager.service failed.
May 2 08:49:50 hibbert gnome-session[2255]: (nm-applet:2452): GLib-CRITICAL **: Source ID 18520 was not found when attempting to remove it

This exact configuration worked just fine before upgrading to Vivid

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu15.1
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May 2 08:52:22 2015
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-03-30 (397 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
IpRoute:
 default via 192.168.0.1 dev wlan0 proto static metric 1024
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.107
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to vivid on 2015-04-30 (1 days ago)
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: Error: nmcli (0.9.10.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running.
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
Oscar Tiderman (oscar-tiderman) wrote :
Revision history for this message
Oscar Tiderman (oscar-tiderman) wrote :

This only happens when IPv6 routes are pushed to the client, as soon as we removed the IPv6 routes I could connect without any issues again.

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
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.