| 2008-10-17 13:45:11 |
Daniel Newman |
bug |
|
|
added bug |
| 2008-11-05 14:41:15 |
DanielRoesler |
bluez-gnome: status |
New |
Confirmed |
|
| 2008-11-05 14:41:15 |
DanielRoesler |
bluez-gnome: statusexplanation |
|
|
|
| 2008-11-10 08:18:31 |
Jonathan Ernst |
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. |
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 cannot be paired anymore.
== 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. |
|
| 2008-11-10 08:18:31 |
Jonathan Ernst |
title |
bluetooth-wizard unable to pair headset |
bluetooth-wizard unable to pair to fixed pin devices |
|
| 2008-11-11 19:27:09 |
tz |
bug |
|
|
added attachment 'bluewizard.patch' (The above text as a patch) |
| 2008-11-12 21:06:10 |
tz |
bug |
|
|
added attachment 'bluewizard.patch2' (Updated ask for pin dialog patch) |
| 2008-11-14 10:05:27 |
Jonathan Ernst |
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 cannot be paired anymore.
== 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. |
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://bugzilla.gnome.org/show_bug.cgi?id=560315
Holux 1000B GPS http://bugzilla.gnome.org/show_bug.cgi?id=560604
Acoustic Research ARWH1 http://bugzilla.gnome.org/show_bug.cgi?id=560605
Holux m-241 GPS http://bugzilla.gnome.org/show_bug.cgi?id=560606
Bluemax Bluetooth GPS Receiver GPS-009 http://bugzilla.gnome.org/show_bug.cgi?id=560609
Navigon Triceiver GPS http://bugzilla.gnome.org/show_bug.cgi?id=560713
HBH-PV700 http://bugzilla.gnome.org/show_bug.cgi?id=560714
Qstarz BT-Q880 GPS http://bugzilla.gnome.org/show_bug.cgi?id=560715
eGPS-397 http://bugzilla.gnome.org/show_bug.cgi?id=560625
Hp Photosmart D5160 http://bugzilla.gnome.org/show_bug.cgi?id=560762
Trust V92 56K Bluetooth Wireless Modem http://bugzilla.gnome.org/show_bug.cgi?id=560763
== 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. |
|
| 2008-11-18 08:43:53 |
Jonathan Ernst |
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://bugzilla.gnome.org/show_bug.cgi?id=560315
Holux 1000B GPS http://bugzilla.gnome.org/show_bug.cgi?id=560604
Acoustic Research ARWH1 http://bugzilla.gnome.org/show_bug.cgi?id=560605
Holux m-241 GPS http://bugzilla.gnome.org/show_bug.cgi?id=560606
Bluemax Bluetooth GPS Receiver GPS-009 http://bugzilla.gnome.org/show_bug.cgi?id=560609
Navigon Triceiver GPS http://bugzilla.gnome.org/show_bug.cgi?id=560713
HBH-PV700 http://bugzilla.gnome.org/show_bug.cgi?id=560714
Qstarz BT-Q880 GPS http://bugzilla.gnome.org/show_bug.cgi?id=560715
eGPS-397 http://bugzilla.gnome.org/show_bug.cgi?id=560625
Hp Photosmart D5160 http://bugzilla.gnome.org/show_bug.cgi?id=560762
Trust V92 56K Bluetooth Wireless Modem http://bugzilla.gnome.org/show_bug.cgi?id=560763
== 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. |
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://bugzilla.gnome.org/show_bug.cgi?id=560315
Holux 1000B GPS http://bugzilla.gnome.org/show_bug.cgi?id=560604
Acoustic Research ARWH1 http://bugzilla.gnome.org/show_bug.cgi?id=560605
Holux m-241 GPS http://bugzilla.gnome.org/show_bug.cgi?id=560606
Bluemax Bluetooth GPS Receiver GPS-009 http://bugzilla.gnome.org/show_bug.cgi?id=560609
Navigon Triceiver GPS http://bugzilla.gnome.org/show_bug.cgi?id=560713
HBH-PV700 http://bugzilla.gnome.org/show_bug.cgi?id=560714
Qstarz BT-Q880 GPS http://bugzilla.gnome.org/show_bug.cgi?id=560715
eGPS-397 http://bugzilla.gnome.org/show_bug.cgi?id=560625
Hp Photosmart D5160 http://bugzilla.gnome.org/show_bug.cgi?id=560762
Trust V92 56K Bluetooth Wireless Modem http://bugzilla.gnome.org/show_bug.cgi?id=560763
OBDPros scantool http://bugzilla.gnome.org/show_bug.cgi?id=561325
Tecom BT Headset http://bugzilla.gnome.org/show_bug.cgi?id=561324
G-Rays1 gps http://bugzilla.gnome.org/show_bug.cgi?id=561326
HUDGPS http://bugzilla.gnome.org/show_bug.cgi?id=561327
Philips Bluetooth Stereo Headset SHB7100 http://bugzilla.gnome.org/show_bug.cgi?id=561328
== 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. |
|
| 2008-11-22 14:43:46 |
CADE20 |
bug |
|
|
added attachment 'gpshack.diff' (Patch for bluez-gnome-1.8/wizard/main.c) |
| 2008-11-22 20:44:09 |
CADE20 |
bug |
|
|
added attachment 'wizardhack.diff' (Patch for bluez-gnome-1.8/wizard/main.c) |
| 2008-12-07 12:07:28 |
Jonathan Ernst |
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://bugzilla.gnome.org/show_bug.cgi?id=560315
Holux 1000B GPS http://bugzilla.gnome.org/show_bug.cgi?id=560604
Acoustic Research ARWH1 http://bugzilla.gnome.org/show_bug.cgi?id=560605
Holux m-241 GPS http://bugzilla.gnome.org/show_bug.cgi?id=560606
Bluemax Bluetooth GPS Receiver GPS-009 http://bugzilla.gnome.org/show_bug.cgi?id=560609
Navigon Triceiver GPS http://bugzilla.gnome.org/show_bug.cgi?id=560713
HBH-PV700 http://bugzilla.gnome.org/show_bug.cgi?id=560714
Qstarz BT-Q880 GPS http://bugzilla.gnome.org/show_bug.cgi?id=560715
eGPS-397 http://bugzilla.gnome.org/show_bug.cgi?id=560625
Hp Photosmart D5160 http://bugzilla.gnome.org/show_bug.cgi?id=560762
Trust V92 56K Bluetooth Wireless Modem http://bugzilla.gnome.org/show_bug.cgi?id=560763
OBDPros scantool http://bugzilla.gnome.org/show_bug.cgi?id=561325
Tecom BT Headset http://bugzilla.gnome.org/show_bug.cgi?id=561324
G-Rays1 gps http://bugzilla.gnome.org/show_bug.cgi?id=561326
HUDGPS http://bugzilla.gnome.org/show_bug.cgi?id=561327
Philips Bluetooth Stereo Headset SHB7100 http://bugzilla.gnome.org/show_bug.cgi?id=561328
== 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. |
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://bugzilla.gnome.org/show_bug.cgi?id=560315
Holux 1000B GPS http://bugzilla.gnome.org/show_bug.cgi?id=560604
Acoustic Research ARWH1 http://bugzilla.gnome.org/show_bug.cgi?id=560605
Holux m-241 GPS http://bugzilla.gnome.org/show_bug.cgi?id=560606
Bluemax Bluetooth GPS Receiver GPS-009 http://bugzilla.gnome.org/show_bug.cgi?id=560609
Navigon Triceiver GPS http://bugzilla.gnome.org/show_bug.cgi?id=560713
HBH-PV700 http://bugzilla.gnome.org/show_bug.cgi?id=560714
Qstarz BT-Q880 GPS http://bugzilla.gnome.org/show_bug.cgi?id=560715
eGPS-397 http://bugzilla.gnome.org/show_bug.cgi?id=560625
Hp Photosmart D5160 http://bugzilla.gnome.org/show_bug.cgi?id=560762
Trust V92 56K Bluetooth Wireless Modem http://bugzilla.gnome.org/show_bug.cgi?id=560763
OBDPros scantool http://bugzilla.gnome.org/show_bug.cgi?id=561325
Tecom BT Headset http://bugzilla.gnome.org/show_bug.cgi?id=561324
G-Rays1 gps http://bugzilla.gnome.org/show_bug.cgi?id=561326
HUDGPS http://bugzilla.gnome.org/show_bug.cgi?id=561327
Philips Bluetooth Stereo Headset SHB7100 http://bugzilla.gnome.org/show_bug.cgi?id=561328
BT-GPS-37A4C2 http://bugzilla.gnome.org/show_bug.cgi?id=563554
== 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. |
|
| 2008-12-30 10:10:17 |
Jandro |
bug |
|
|
assigned to bluez-gnome (Fedora) |
| 2009-01-15 00:32:32 |
pumber |
bug |
|
|
added attachment 'Itech_S38.jpg' (Itech_S38.jpg) |
| 2009-01-19 13:48:35 |
Martin Pitt |
bug |
|
|
assigned to bluez-gnome |
| 2009-01-20 01:51:04 |
Bug Watch Updater |
bluez-gnome: status |
Unknown |
Confirmed |
|
| 2009-03-05 00:26:09 |
Jordan |
bluez-gnome: status |
Confirmed |
Unknown |
|
| 2009-03-05 00:26:09 |
Jordan |
bluez-gnome: statusexplanation |
|
Bug 560315 was about a specific device and it was made clear that discussion about a general solution for fixed pin devices should be moved elsewhere. |
|
| 2009-03-09 08:33:28 |
Martin Pitt |
bluez-gnome: status |
Confirmed |
In Progress |
|
| 2009-03-09 08:33:28 |
Martin Pitt |
bluez-gnome: assignee |
|
pitti |
|
| 2009-03-09 08:33:28 |
Martin Pitt |
bluez-gnome: importance |
Undecided |
High |
|
| 2009-03-09 08:33:28 |
Martin Pitt |
bluez-gnome: statusexplanation |
|
This affects a lot of bluetooth devices, and fix was committed upstream. We ought to fix this in Jaunty. |
|
| 2009-03-10 01:24:37 |
Bug Watch Updater |
bluez-gnome: status |
Unknown |
Fix Released |
|
| 2009-03-16 12:40:06 |
Launchpad Janitor |
bluez-gnome: status |
In Progress |
Fix Released |
|
| 2009-03-20 16:39:30 |
Balázs Grill |
bluez-gnome: status |
New |
Confirmed |
|
| 2009-03-20 16:39:30 |
Balázs Grill |
bluez-gnome: statusexplanation |
|
|
|
| 2009-03-30 10:34:48 |
Baptiste Mille-Mathias |
bug watch added |
|
https://bugzilla.redhat.com/show_bug.cgi?id=472686 |
|
| 2009-03-30 10:34:48 |
Baptiste Mille-Mathias |
bluez-gnome (Fedora): importance |
Undecided |
Unknown |
|
| 2009-03-30 10:34:48 |
Baptiste Mille-Mathias |
bluez-gnome (Fedora): status |
Confirmed |
Unknown |
|
| 2009-03-30 10:35:03 |
Bug Watch Updater |
bluez-gnome: status |
Unknown |
Fix Released |
|
| 2009-04-24 18:12:01 |
Manowar |
removed subscriber Manowar |
|
|
|
| 2009-07-02 23:53:07 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic/bluez-gnome |
|
| 2010-09-16 05:54:24 |
Bug Watch Updater |
bluez-gnome: importance |
Unknown |
Medium |
|
| 2012-05-22 08:25:13 |
Gunnar Thielebein |
removed subscriber Gunnar Thielebein |
|
|
|
| 2017-10-27 08:13:59 |
Bug Watch Updater |
bluez-gnome (Fedora): importance |
Unknown |
Medium |
|
