bluetooth-applet crashed with SIGSEGV in g_simple_async_result_complete()

[Scott Moser]

This seems to happen fairly frequently to me when I select 'disconnect' from the bluetooth menu.
I'm not sure if it is when the device has been manually turned off that triggers it or not.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-bluetooth 3.5.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Tue Aug 28 12:37:53 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: bluetooth-applet
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f35e96a07a0: mov 0x8(%rax),%rcx
 PC (0x7f35e96a07a0) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /usr/lib/libgnome-bluetooth.so.11
 g_simple_async_result_complete (simple=0x2068630) at /build/buildd/glib2.0-2.33.10/./gio/gsimpleasyncresult.c:775
 reply_cb (connection=<optimized out>, res=0x20934b0, user_data=user_data@entry=0x2068630) at /build/buildd/glib2.0-2.33.10/./gio/gdbusproxy.c:2632
 g_simple_async_result_complete (simple=0x20934b0) at /build/buildd/glib2.0-2.33.10/./gio/gsimpleasyncresult.c:775
 g_dbus_connection_call_done (source=0x1f4c180, result=<optimized out>, user_data=user_data@entry=0x211ec40) at /build/buildd/glib2.0-2.33.10/./gio/gdbusconnection.c:5339
Title: bluetooth-applet crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: Upgraded to quantal on 2011-11-07 (295 days ago)
UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare sbuild

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