NetworkManager segfaults on connect

Bug #1521136 reported by Ben Howard
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Upon connecting, NetworkManager from -updates is segfaulting:

[ 139.520739] NetworkManager[15884]: segfault at 0 ip 0000000000497ad7 sp 00007fff77195d00 error 4 in NetworkManager[400000+1bf000]

Nov 30 10:31:23 arbella NetworkManager[16259]: <info> keyfile: add connection in-memory (c4b6e184-67e3-4a12-8dd3-79ec7ef650e0,"enx803f5d087a34")
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (enx803f5d087a34): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (enx803f5d087a34): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41]
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (enx803f5d087a34): Activation: starting connection 'enx803f5d087a34' (c4b6e184-67e3-4a12-8dd3-79ec7ef650e0)
Nov 30 10:31:23 arbella NetworkManager[16259]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (lo): link connected
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (wlp2s0): using nl80211 for WiFi device control
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (wlp2s0): driver supports Access Point (AP) mode
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (wlp2s0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'ath10k_pci', ifindex: 3)
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (wlp2s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Nov 30 10:31:23 arbella kernel: [ 140.168048] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> urfkill disappeared from the bus
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> use BlueZ version 5
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> wpa_supplicant running
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (wlp2s0): supplicant interface state: starting -> ready
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (lxcbr0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> (enx803f5d087a34): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Nov 30 10:31:23 arbella NetworkManager[16259]: <info> Policy set 'enx803f5d087a34' (enx803f5d087a34) as default for IPv4 routing and DNS.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: Network-Manager 1.0.4-0ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 30 10:39:36 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-11-21 (9 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
 default via 10.20.64.1 dev wlp2s0 proto static metric 600
 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1
 10.20.64.0/21 dev wlp2s0 proto kernel scope link src 10.20.66.104 metric 600
 169.254.0.0/16 dev lxcbr0 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 lxcbr0 bridge connected /org/freedesktop/NetworkManager/Devices/3 lxcbr0 ac91e68a-905e-4cd2-a937-11b8c5f4bed0 /org/freedesktop/NetworkManager/ActiveConnection/1
 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Canonical-2.4GHz-g 4eb6b0d8-a49e-4e11-aff1-18ce3f158523 /org/freedesktop/NetworkManager/ActiveConnection/2
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- --
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
Ben Howard (darkmuggle-deactivatedaccount) wrote :
Revision history for this message
Ben Howard (darkmuggle-deactivatedaccount) wrote :

Downgrading (i.e. sudo apt-get -y --reinstall install --force-yes network-manager=1.0.4-0ubuntu5) and then rebooting fixed me.

Revision history for this message
Maximilian (mkoegel) wrote :

Same problem here. Downgrading does not fix the problem for me though...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks, when you say "from updates" is it 5.1 or 5.2 from proposed rather? Could you get a stacktrace of the segfault?

Changed in network-manager (Ubuntu):
importance: Undecided → High
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
Vlad Firoiu (vladfi2) wrote :

This just started happening to me after a update. According to apt-cache policy I have network-manager version 1.0.4-0ubuntu5.2 installed.

Revision history for this message
Vlad Firoiu (vladfi2) wrote :

This just started happening to me after a recent update. According to apt-cache policy I have network-manager version 1.0.4-0ubuntu5.2 installed.

Revision history for this message
andrew.jeffery (andrew-aj) wrote :

I ran into this issue. Looking at the code and the patches submitted upstream, it appears this commit should fix the issue:

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=956577a24640cb96f6255417073d52230c573ed4

Revision history for this message
Edward Z. Yang (ezyang) wrote :

Confirmed downgrading fixes the problem.

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.