bluetooth-applet crashed with SIGSEGV in g_closure_invoke()

StacktraceTop:
 create_treeview (self=0x1c716f0) at bluetooth-chooser.c:847
 bluetooth_chooser_init (self=0x1c716f0) at bluetooth-chooser.c:933
 ?? ()
 ?? ()

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

hi,
1. set up a new bluetooth device. So fareverything went well. Then I asked
to navigate the files on your device. I tried a SamsungC3510 and Android
2.3 and the behavior was the same in both.
2. In versions prior to 11.10, when I wanted tobrowse files on the device
from the bluetoothmenu, the manager Nautilus openedautomatically on the
device and allowed the immediate viewing of files and folders.
3. This no longer happens. I have to openNautilus manually. And then when I
select the device from the sidebar, the Nautilus does not show its content
and gives the reported error.
I hope this information is sufficient. I can, if necessary, make screen
captures of all of the steps I take. If it helps, just ask.
regards
paulo

2012/2/2 Sebastien Bacher <email address hidden>

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately, we cannot work on this bug because your
> description didn't include enough information. You may find it helpful
> to read "How to report bugs effectively"
> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
> if you would then provide a more complete description of the problem.
>
> We have instructions on debugging some types of problems at
> http://wiki.ubuntu.com/DebuggingProcedures
>
> At a minimum, we need:
> 1. the specific steps or actions you took that caused you to encounter the
> problem,
> 2. the behavior you expected, and
> 3. the behavior you actually encountered (in as much detail as possible).
> Thanks!
>
> ** Changed in: gnome-bluetooth (Ubuntu)
> Importance: Medium => Low
>
> ** Changed in: gnome-bluetooth (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/876532
>
> Title:
> bluetooth-applet crashed with SIGSEGV in g_closure_invoke()
>
> Status in “gnome-bluetooth” package in Ubuntu:
> Incomplete
>
> Bug description:
> Can't open bluetooth devices in nautilus.
> Can't navigate on devices files system.
> Also get this error in nautilus: "Erro: DBus error
> org.freedesktop.DBus.Error.ServiceUnknown: The name :1.108 was not provided
> by any .service files. Select other visualizer and try again."
>
> ProblemType: Crash
> DistroRelease: Ubuntu 11.10
> Package: gnome-bluetooth 3.2.0-0ubuntu1
> ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
> Uname: Linux 3.0.0-12-generic x86_64
> ApportVersion: 1.23-0ubuntu3
> Architecture: amd64
> CasperVersion: 1.287
> Date: Mon Oct 17 14:22:21 2011
> ExecutablePath: /usr/bin/bluetooth-applet
> LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
> ProcCmdline: bluetooth-applet
> ProcEnviron:
> PATH=(custom, no user)
> LANG=pt_PT.UTF-8
> SHELL=/bin/bash
> SegvAnalysis:
> Segfault happened at: 0x7fb3c4a4da64: cmpl $0x1,0x80(%rax)
> PC (0x7fb3c4a4da64) 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
> ?...

[Expired for gnome-bluetooth (Ubuntu) because there has been no activity for 60 days.]

This bug will not be corrected?
Continues to happen exactly as was originally reported.
The solution is then what, for those who want to use Ubuntu and can not access external devices by Bluetoth?

[Expired for gnome-bluetooth (Ubuntu) because there has been no activity for 60 days.]