NetworkManager crashed with SIGSEGV in nm_active_connection_get_path()

[Michał Sawicz]

I believe I was switching between two networks, maybe the same, but changing passwords?

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
NonfreeKernelModules: wl nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
Date: Tue Mar 25 20:39:29 2014
ExecutablePath: /usr/sbin/NetworkManager
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
 WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x453265 <nm_active_connection_get_path+21>: mov 0x8(%rax),%rax
 PC (0x00453265) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 nm_active_connection_get_path ()
 ?? ()
 g_object_get_property () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in nm_active_connection_get_path()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-03-19T03:42:53.511638
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 /hso_0 gsm disconnected /org/freedesktop/NetworkManager/Devices/2
 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/1
 em1 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.8 connected enabled disabled disabled enabled disabled

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1232146, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.