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

[V3g3t0X]

It had something to do with blue proximity app that I was trying to run.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.1.92-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
Date: Sun Sep 25 00:55:52 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu-Netbook-Remix 9.10 "Karmic Koala" - Release i386 (20091028.4)
ProcCmdline: gnome-control-center bluetooth
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8488fe <g_type_check_instance_cast+46>: mov (%edx),%eax
 PC (0x008488fe) ok
 source "(%edx)" (0x00000011) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/gnome-bluetooth/plugins/libnma.so
 g_cclosure_marshal_VOID__PARAM () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to oneiric on 2011-09-23 (2 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare vboxusers video
usr_lib_gnome-control-center:
 deja-dup 19.92-0ubuntu2
 gnome-bluetooth 3.1.92-0ubuntu1
 indicator-datetime 0.2.95-0ubuntu1

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #828436, 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.