bluetooth-applet crashed with SIGSEGV in g_closure_invoke()

[Shock]

I chose the "Browse files on device" action and it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-bluetooth 3.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-15.25-generic 3.0.13
Uname: Linux 3.0.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sun Jan 8 12:20:08 2012
ExecutablePath: /usr/bin/bluetooth-applet
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: bluetooth-applet
SegvAnalysis:
 Segfault happened at: 0x7fc3c89b4cf4: cmpl $0x1,0x80(%rax)
 PC (0x7fc3c89b4cf4) ok
 source "$0x1" ok
 destination "0x80(%rax)" (0x00000080) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-bluetooth
StacktraceTop:
 ?? () from /usr/lib/libgnome-bluetooth.so.8
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 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
Title: bluetooth-applet crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to oneiric on 2011-12-15 (23 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (bluetooth-applet:2332): Gtk-CRITICAL **: gtk_tree_path_get_depth: assertion `path != NULL' failed
 (bluetooth-applet:2332): Gtk-CRITICAL **: gtk_tree_path_get_depth: assertion `path != NULL' failed
 (gnome-control-center:2656): Gtk-CRITICAL **: gtk_tree_path_get_depth: assertion `path != NULL' failed
 (gnome-control-center:2656): Gtk-CRITICAL **: gtk_tree_path_get_depth: assertion `path != NULL' failed

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