[network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi()

[Jens Kehne]

Here is what I did right before the crash: I opened the network settings, added an openvpn account, then connected to that account without first closing the network settings window. The network settings window then disappeared, but the connection was established successfully.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.2-0ubuntu0.5
Uname: Linux 3.5.4-zen+ x86_64
NonfreeKernelModules: apwr3_0
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Thu Sep 27 14:29:06 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: gnome-control-center network
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffcf4577246 <nm_device_get_udi+22>: cmp %rax,(%rdx)
 PC (0x7ffcf4577246) ok
 source "%rax" ok
 destination "(%rdx)" (0x000005fb) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 nm_device_get_udi () from /usr/lib/libnm-glib.so.4
 ?? () from /usr/lib/control-center-1/panels/libnetwork.so
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: [network]: gnome-control-center crashed with SIGSEGV in nm_device_get_udi()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare src sudo tracing vboxusers wireshark
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.4-0ubuntu3
 deja-dup 22.0-0ubuntu2
 gnome-bluetooth 3.2.2-0ubuntu5
 indicator-datetime 0.3.94-0ubuntu2

[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 #985191, 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.