gnome-control-center crashed with SIGSEGV in add_connection_info_find()

Bug #946014 reported by James Tait
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Medium
Unassigned

Bug Description

I'm not 100% sure when the crash actually happened. I enabled Bluetooth and removed previous paring with my phone. Then I attempted to pair with my computer from my phone, but the crash dialogue appeared.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.3.90-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
CheckboxSubmission: dd3689fa6394f60ec14dbe98d0bab891
CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
Date: Sun Mar 4 00:21:42 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: gnome-control-center bluetooth
SegvAnalysis:
 Segfault happened at: 0x7fc279b814ac: mov 0x28(%rax),%rdx
 PC (0x7fc279b814ac) ok
 source "0x28(%rax)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/libnm-glib.so.4
 ?? () from /usr/lib/libnm-glib.so.4
 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 crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2012-01-13 (50 days ago)
UserGroups: adm admin cdrom dialout disk libvirtd lpadmin plugdev sambashare vde2-net
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.2-0ubuntu3
 deja-dup 21.90-0ubuntu1
 gnome-bluetooth 3.2.2-0ubuntu3
 indicator-datetime 0.3.90-0ubuntu1

Revision history for this message
James Tait (jamestait) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 add_connection_info_find (self=0x7fc29d2f5c00, connection=0x7fc29d34da80) at nm-remote-settings.c:120
 connection_removed_cb (remote=0x7fc29d34da80, user_data=<optimized out>) at nm-remote-settings.c:210
 g_closure_add_invalidate_notifier (closure=0x7fc29d355db0, notify_data=0x0, notify_func=0) at /build/buildd/glib2.0-2.31.20/./gobject/gclosure.c:467
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x8002, hash_table=0x0) at /build/buildd/glib2.0-2.31.20/./glib/ghash.c:401
 g_hash_table_lookup (hash_table=0x0, key=0x8002) at /build/buildd/glib2.0-2.31.20/./glib/ghash.c:1074

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
summary: - gnome-control-center crashed with SIGSEGV in g_closure_invoke()
+ gnome-control-center crashed with SIGSEGV in add_connection_info_find()
tags: removed: need-amd64-retrace
visibility: private → public
affects: gnome-control-center (Ubuntu) → network-manager (Ubuntu)
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.