gnome-control-center.real crashed with SIGSEGV in net_device_get_nm_device()

Bug #1412108 reported by Luke Faraone
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Probably the same as bug 1367005, but maybe we'll actually get usable debugging data here.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gnome-control-center 1:3.12.1-5ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Jan 17 20:04:42 2015
ExecutablePath: /usr/bin/gnome-control-center.real
InstallationDate: Installed on 2013-03-18 (671 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214)
ProcCmdline: /usr/bin/gnome-control-center.real network show-device /org/freedesktop/NetworkManager/Devices/0
SegvAnalysis:
 Segfault happened at: 0x50ace4 <net_device_get_nm_device+4>: mov (%rax),%rax
 PC (0x0050ace4) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 net_device_get_nm_device ()
 ?? ()
 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: gnome-control-center.real crashed with SIGSEGV in net_device_get_nm_device()
UpgradeStatus: Upgraded to utopic on 2014-10-27 (83 days ago)
UserGroups: adm cdrom dip fuse kvm libvirtd lpadmin netdev plugdev sambashare sbuild sudo

Revision history for this message
Luke Faraone (lfaraone) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 net_device_get_nm_device ()
 ?? ()
 g_closure_invoke (closure=0x2c87870, return_value=0x0, n_param_values=2, param_values=0x7fff1a354c10, invocation_hint=0x7fff1a354bb0) at /build/buildd/glib2.0-2.42.1/./gobject/gclosure.c:768
 signal_emit_unlocked_R (node=node@entry=0x11f0750, detail=detail@entry=3787, instance=instance@entry=0x2b82580, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fff1a354c10) at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c:3553
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fff1a354da0) at /build/buildd/glib2.0-2.42.1/./gobject/gsignal.c:3309

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Luke Faraone (lfaraone)
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
tags: added: vivid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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