bluetooth-wizard crashes when the name of a discovered device is NULL

Bug #1080656 reported by Till Kamppeter on 2012-11-19
54
This bug affects 11 people
Affects Status Importance Assigned to Milestone
ubuntu-nexus7
Undecided
Unassigned
gnome-bluetooth (Ubuntu)
High
Unassigned

Bug Description

If you scan for pairing-ready Bluetooth devices and one of the device's names is NULL, bluetooth-wizard shows the alias based on the devices address, like 00-26-55-09-6A-9C (and "bt-adapter -d" of bluez-tools shows "Name: (null)"). If you click on such an entry in bluetooth-wizard (or move the selection to such an entry with the cursor keys), the wizard simply crashes, making it impossible to pair this device.

I observed this in Quantal both on a standard 64-bit Intel PC and on the Nexus 7.
---
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
DistroRelease: Ubuntu 12.10
InstallationDate: Installed on 2012-07-27 (115 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
MarkForUpload: True
Package: gnome-bluetooth 3.6.0-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
Tags: quantal running-unity
Uname: Linux 3.5.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
---
ApportVersion: 2.6.1-0ubuntu3
Architecture: armhf
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-newark-quantal-armhf-20121026-1
DistroRelease: Ubuntu 12.10
Package: gnome-bluetooth 3.6.0-0ubuntu1
PackageArchitecture: armhf
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: quantal running-unity
Uname: Linux 3.1.10-6-nexus7 armv7l
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin nopasswdlogin plugdev sudo

apport information

affects: cups (Ubuntu) → gnome-bluetooth (Ubuntu)
tags: added: apport-collected quantal running-unity
description: updated
Till Kamppeter (till-kamppeter) wrote :

apport information

description: updated
Changed in gnome-bluetooth (Ubuntu):
importance: Undecided → High
Chris Wayne (cwayne18) wrote :

Just adding a note here that since Bluetooth is not yet officially working on the Nexus 7, I am going to wait to try and reproduce until we have an official fix. I'm a bit concerned about testing with such a workaround.

Till Kamppeter (till-kamppeter) wrote :

Note that the problem also occurs on Intel-based PCs, so until the bluetoothd crasher on the Nexus 7 is fixed it can be investigated on the PC platform. Probably the fix is even the same on both platforms.

Launchpad Janitor (janitor) wrote :

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

Changed in gnome-bluetooth (Ubuntu):
status: New → Confirmed

No, we can't really say it's a duplicate yet -- this bug is missing a backtrace for the crash.

Till, would you be able to reproduce the crasher (given that it's likely tied to that particular device you used not reporting a bluetooth name), and attach/paste a backtrace?

Changed in gnome-bluetooth (Ubuntu):
status: Confirmed → Incomplete
Changed in ubuntu-nexus7:
status: New → Incomplete
Rolo (rolo-wildfish) wrote :

I've experienced this issue today and possibly come up with a workaround.

Ubuntu 12.10 x64. USB bluetooth dongle. Let me know if you need any further hardware info.

Initially, when scanning for devices, some sort of ID of the device was displayed (a hex UID type string). Any time I clicked on this the applet crashed and I saw the crash report for "bluetooth-wizard".

I did this a few times, but then I tried again and waited patiently whilst it continued to search for devices. Eventually the hardware ID listed changed into the name of my BT headset. Now when I click to select, and click Continue, I get no error at this point (it doesn't connect to the device in the end, but I'd wager that's a different issue).

Hope that's useful to someone.

Mike Loebl (mloebl) wrote :

I believe am seeing the same problem trying to pair a Microsoft Bluetooth Wireless Laser Mouse 8000 as it shows just the hw address, and if I select it, it crashes. Also interesting to note this device I believe has no PIN, though not sure if that matters.

I have attached the backtrace (hopefully I did this correctly.) If I add a Bluetooth device that has a name (such as my phone), it pairs no problem.

Mike Loebl (mloebl) wrote :

I should note I am seeing this on Ubuntu 12.10 x64 on a desktop pc, not the Nexus 7 as original bug was logged as.

tags: added: mobile nexus7
tags: added: amd64
Sasa Paporovic (melchiaros) wrote :

Regarding to mloebl who provide a stacktrace of the probem(even if it is with amd64 architecture), setting the status of the report back to confirmed.

Changed in gnome-bluetooth (Ubuntu):
status: Incomplete → Confirmed
Changed in ubuntu-nexus7:
status: Incomplete → Confirmed
Ryan Harper (raharper) wrote :

I've got a ZelHer P20 headset and a W520 Lenovo laptop, the same problem occurs.

What I observed is that during the first 60 seconds of activating the P20 headset, running bt-adapter -d will display the Name: (null) and in the bluetooth-wizard, it only shows the bt address (mac-like format).

After about 60 seconds of the headset in pairing mode, re-running bt-adapter-d, the name field is now populated. After the name field is present, pairing can be complete.

So, while clearly gnome-bluetooth should handle the case where name is null, there may be a workaround if you can keep your device in pairing mode long enough so that the name of the adapter appears.

Mike Loebl (mloebl) wrote :

I updated to 13.04, and I can now add the mouse that was crashing 12.10 before thru bluetooth-wizard. However, I do lose the mouse at some point (still trying to determine why it disconnects at some point, but may be unrelated to ubuntu.)

Kevin (colwellkr) wrote :

The work around it post 8 worked for me, I was having the issues everyone else was and the workaround in post 8 made it all work!

Thanks guys!

Daniel van Vugt (vanvugt) wrote :

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

Changed in gnome-bluetooth (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers