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

[Matthew Woerly]

I wanted to pair my Bluetooth headphones (like I have done before).
I went to the Bluetooth settings and turned on the connection for the headphones. The switch stayed on, but it didn't connect. If I went to the sound settings, the headphones would not show up. Eventually, this crash would just happen.
I tried this on a different computer running 32-bit and it did the same thing.
Using the Ubuntu Bluetooth indicator finally worked.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-bluetooth 3.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-15.26-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 7 23:47:45 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: gnome-control-center bluetooth
SegvAnalysis:
 Segfault happened at: 0x7fcb0432a15b: mov 0x8(%rax),%rdi
 PC (0x7fcb0432a15b) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /usr/lib/libgnome-bluetooth.so.8
 ?? () from /usr/lib/control-center-1/panels/libbluetooth.so
 ?? () from /usr/lib/control-center-1/panels/libbluetooth.so
 ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: gnome-control-center crashed with SIGSEGV in dbus_connection_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

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