bluetooth-applet crashes when trying to browse device

Bug #880079 reported by Frederik Elwert
198
This bug affects 31 people
Affects Status Importance Assigned to Milestone
GNOME Bluetooth
Expired
Critical
OEM Priority Project
Won't Fix
High
Unassigned
Oneiric
Fix Released
High
James M. Leddy
Precise
Invalid
Undecided
Unassigned
Quantal
Won't Fix
High
Unassigned
gnome-bluetooth (Ubuntu)
Won't Fix
High
James M. Leddy
Nominated for Oneiric by James M. Leddy
Nominated for Precise by James M. Leddy

Bug Description

When trying to browse a device using the bluetooth applet, it crashes.

Steps to reproduce:
1. In the bluetooth applet, choose “Browse files on device...”
2. Select the device and click “Browse”

The applet does not crash when using the device submenu “Device → Browse files...”. It still fails to browse.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-bluetooth 3.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Sat Oct 22 22:23:40 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110803.1)
SourcePackage: gnome-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Frederik Elwert (frederik-elwert) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-bluetooth (Ubuntu):
status: New → Confirmed
Revision history for this message
Justin (parksjw) wrote :

I can confirm the same under Oneiric and I believe I also experienced this under Natty, but I'm not certain about Natty as it has been a while. I'm adding a trace when using browse off the first menu (where the applet crashes) and a trace when using the device submenu and selecting browse. As an added bonus, this often causes my phone to shutdown or restart.

Revision history for this message
Justin (parksjw) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you install gnome-bluetooth-dbgsym libgnome-bluetooth8-dbgsym (see https://wiki.ubuntu.com/DebuggingProgramCrash for details on how to do that) and get a new valgrind log? Could you also get the stacktrace using gdb or enable apport in /etc/default/apport and use it to send the bug?

Changed in gnome-bluetooth (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
Justin (parksjw) wrote :

Here's the log under the crash condition with the debug symbols installed.

Revision history for this message
Justin (parksjw) wrote :

Furthermore, here's the console output from the previously attached valgrind log session.

Revision history for this message
Michael Berg (jaykaycgn) wrote :

disappointing, the first time i want to use bluetooth on my computer and then it crashes ... :P

Dec 21 21:10:07 tavor kernel: [ 913.441246] bluetooth-apple[2842]: segfault at 80 ip 00007fef57b2bcf4 sp 00007fff09afa040 error 4 in libgnome-bluetooth.so.8.0.0[7fef57b1b000+1a000]

Kent Baxley (kentb)
Changed in oem-priority:
importance: Undecided → High
Changed in oem-priority:
status: New → Confirmed
Revision history for this message
Kent Baxley (kentb) wrote :

Here's a gdb stack trace from a crash I experienced.

Changed in gnome-bluetooth (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kent Baxley (kentb) wrote :

The applet crash itself appears to be fixed in 12.04 with Gnome 3.2.1-1ubuntu3

Revision history for this message
Kent Baxley (kentb) wrote :

Precise bug where a fix went in to take care of the tiny window, but, it also seems to take care of the segfaults:

https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/829703

Revision history for this message
James M. Leddy (jm-leddy) wrote :

Hi kent,

I can confirm that the patch in bug 829703, while making the window more presentable, doesn't actually fix the crash. I'll bisect the code tomorrow and find out what we can actually do to fix this.

Revision history for this message
James M. Leddy (jm-leddy) wrote :

Hi kent,

One of the variables was freed too many times. I think the only reason that this doesn't fail in precise is because the obex browse actually succeeds, and as a result the applet doesn't redisplay the dialog. In any case bluetooth-applet should be fixed to handle this failure case.

Revision history for this message
James M. Leddy (jm-leddy) wrote :
Revision history for this message
James M. Leddy (jm-leddy) wrote :

The crash can easily be fixed. Unfortunately, you still won't be able to browse devices until bug 879923 is fixed.

Changed in gnome-bluetooth (Ubuntu):
assignee: nobody → James M. Leddy (jm-leddy)
status: Confirmed → In Progress
Changed in gnome-bluetooth:
importance: Unknown → Critical
status: Unknown → Incomplete
Revision history for this message
James M. Leddy (jm-leddy) wrote :

related to bug 899858 . If fixing that bug does not fix the problem we'll investigate a fix for the applet.

Revision history for this message
James M. Leddy (jm-leddy) wrote :

Fixing bug 899858 does not fix this bug. Interestingly, if the user selects the device itself and then selects browse, it works. It's just on first login when they select browse without the phone having been mounted before that this causes a problem.

Revision history for this message
James M. Leddy (jm-leddy) wrote :

If anyone is running precise and can test if this is still an issue I would appreciate commenting here.

Revision history for this message
Frederik Elwert (frederik-elwert) wrote :

I am running Precise, and this seems not to be an issue anymore. I just browsed my N9 via bluetooth, and it worked quite fine.

Revision history for this message
Jim Rhodes (jim-deadlock) wrote :

Likewise, resolved in 12.04

Changed in gnome-bluetooth:
status: Incomplete → Expired
Revision history for this message
Steve White (stevan-white) wrote :

Still crashing in 12.10.

Changed in gnome-bluetooth (Ubuntu):
status: In Progress → Won't Fix
Revision history for this message
Ara Pulido (ara) wrote :

Marking it as won't fix, as the bug only shows when the rest of the bt stack does not work

Changed in oem-priority:
status: Opinion → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.