bluetooth-wizard unable to pair to fixed pin devices
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez-gnome |
Fix Released
|
Medium
|
|||
bluez-gnome (Fedora) |
Fix Released
|
Medium
|
|||
bluez-gnome (Ubuntu) |
Fix Released
|
High
|
Martin Pitt | ||
Jaunty |
Fix Released
|
High
|
Martin Pitt |
Bug Description
This is a regression between Hardy and Intrepid
== Regression details ==
Discovered in version: Intrepid
Last known good version: Hardy
== Affected use cases/hardware ==
Any bluetooth peripheral that has a fixed pin which is not handled by the hardcoded algorithm upstream uses.
Some examples :
X3 Micro headset http://
Holux 1000B GPS http://
Acoustic Research ARWH1 http://
Holux m-241 GPS http://
Bluemax Bluetooth GPS Receiver GPS-009 http://
Navigon Triceiver GPS http://
HBH-PV700 http://
Qstarz BT-Q880 GPS http://
eGPS-397 http://
Hp Photosmart D5160 http://
Trust V92 56K Bluetooth Wireless Modem http://
OBDPros scantool http://
Tecom BT Headset http://
G-Rays1 gps http://
HUDGPS http://
Philips Bluetooth Stereo Headset SHB7100 http://
BT-GPS-37A4C2 http://
== Known workaround ==
none (besides using Ubuntu Hardy)
== Description ==
Binary package hint: bluez-gnome
using bluez-gnome version 1.8-0ubuntu1
ubuntu 8.10 intrepid
Tried to pair with a bluetooth headset. Started bluetooth-wizard, with headset in pairing mode. Headset detected OK and shown on the "Device search" display. Selected it and clicked "Forward". Under "Device setup", got message "setting up new device", then "Connecting to X3 micro now".
Then, "Please enter the following PIN code: 0000" flashed up and vanished, followed by "Pairing with X3 micro failed".
In fact, because it's a headset, there is no way to enter a pin code on it, and I presume this is why the failure occurred. What is needed is for the bluetooth-wizard to prompt for the headset's pin code and send that to the headset, rather than the other way around as is set up at present.
Related branches
Changed in bluez-gnome: | |
status: | New → Confirmed |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in bluez-gnome: | |
status: | Unknown → Confirmed |
Changed in bluez-gnome: | |
status: | Confirmed → Unknown |
Changed in bluez-gnome: | |
assignee: | nobody → pitti |
importance: | Undecided → High |
status: | Confirmed → In Progress |
Changed in bluez-gnome: | |
status: | Unknown → Fix Released |
Changed in bluez-gnome: | |
status: | New → Confirmed |
Changed in bluez-gnome: | |
status: | Unknown → Fix Released |
Changed in bluez-gnome: | |
importance: | Unknown → Medium |
Changed in bluez-gnome (Fedora): | |
importance: | Unknown → Medium |
I worked around this by editing the source of wizard/main.c, changing the default value of 0000 to the correct one for my headset. See below:
/* Most headsets are using 0000 as pincode */ TYPE_HEADSET ||
target_ type == BLUETOOTH_ TYPE_HEADPHONE)
pincode = "1234";
if (target_type == BLUETOOTH_
text = g_strdup_ printf( _("Please enter the following PIN code: %s"),
pincode) ;
However, this isn't really a satisfactory solution. The wizard needs to offer the option of changing the pin code to match whatever hardware is to be paired.