Comment 0 for bug 949743

The crash is reported while using the bluetooth settings. The way to trigger it:
1. While bluetooth is enabled - open bluetooth settings, everything works.
2. Turn off bluetooth using laptop wireless killswitch (I'm on Thinkpad W500)
3. Turn on the killswitch
4. Bluetooth settings don't reflect the fact that bluetooth is enabled (cannot enable or disable in settings) now and a crash is reported.
5. Restarting bluetooth service fixes the settings behaviour

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.3.91-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 7 23:50:03 2012
ExecutablePath: /usr/bin/gnome-control-center
ProcCmdline: gnome-control-center bluetooth
 Segfault happened at: 0x7f0fc6cfc4ac: mov 0x28(%rax),%rdx
 PC (0x7f0fc6cfc4ac) 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
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/
 ?? () from /usr/lib/x86_64-linux-gnu/
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/
Title: gnome-control-center crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
 activity-log-manager-control-center 0.9.3-0ubuntu1
 gnome-bluetooth 3.2.2-0ubuntu3
 indicator-datetime 0.3.90-0ubuntu1