bluetooth-wizard unable to pair to fixed pin devices

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 */
        if (target_type == BLUETOOTH_TYPE_HEADSET ||
                                target_type == BLUETOOTH_TYPE_HEADPHONE)
                pincode = "1234";

        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.

I can confirm this bug. Where can I find and download the source code to confirm the workaround works?

It is also being discussed on ubuntu forums:
http://ubuntuforums.org/showthread.php?p=6010406

I personally think the solution to this bug should be to offer a few options right after you do the device select screen. They should be preselected depending on the device you are using.

(1) Randomly chosen PIN number that you enter on the device (Good for keyboards)
(2) Preselected common PIN number (Typically 0000 or 1234, show in the UI)
(3) Enter a PIN number

I can confirm this bug while trying to attach my HOLEX bluetooth gps receiver to my HP laptop with integrated bluetooth. Other devices like my phone and nokia internet tablet work fine because i can enter in the required pin, but for other devices like my GPS and headset, I cannot enter a pin on the device. The suggestion by Mario would be optimal in this instance.

This one affects me as well. i think i see a request to enter a random pin that i'm supposed to type into my bluetooth device flashing before i get the "Pairing with ... failed" message. i consider this a serious issue as it's a real showstopper for bluetooth users.

Please fix this! This is going to kill me when the release comes out and I still can't use my headset...

Yes. this happens with me too in the release of intrepid. my motorolla bluetooth audio gateway has the default pin of 0000. the applet keeps pairing with a random pin and doesnt let me choose 0000.

i can confirm this bug also. Fails pairing with the oncourse GPS receiver. I see something flash real quick before the failure happens. I need to be able to enter the pincode of this device. Which is 0000. Does not le tme do this.

@Daniel

What is the exact path to the Main.c file you editied. i would like to try your workaroubnd but cannot find the file.

My bluetooth modem has a fixed PIN, therefore I have to specifiy a PIN on my computer. A random PIN is in no way helpful. Please fix this bug.

on 03/11/08 08:27 secion8 said the following:
> i can confirm this bug also. Fails pairing with the oncourse GPS
> receiver. I see something flash real quick before the failure happens. I
> need to be able to enter the pincode of this device. Which is 0000. Does
> not le tme do this.
>
> @Daniel
>
> What is the exact path to the Main.c file you editied. i would like to
> try your workaroubnd but cannot find the file.
>
bluez-gnome-1.8/wizard/main.c

Same for me. I am trying to pair with a BT-Q880 GPS receiver and obviously, there is no way to enter a PIN so bluetooth in Intrepid is now useless for anything except keyboards.

What is surprising about this bug is that keyboards and phones are the only bluetooth devices on which you can normally enter a PIN so if this had been tested on any other device (eg mice, GPS, headsets etc) then the bug would have been immediately apparent.

There have been extensive changes to bluetooth in Intrepid which so far have had two major drawbacks (in addition to this but, blueman no longer works at all and I like it a lot better than the built-in bluetooth utilities) and no advantages. I dare say that there was a good reason for the changes and I appreciate all the hard work that the devs have put into this, but the end result is a big step backward from Hardy.

Same for me. I am trying to pair with a BT-Q880 GPS receiver and obviously, there is no way to enter a PIN so bluetooth in Intrepid is now useless for anything except keyboards.

What is surprising about this bug is that keyboards and phones are the only bluetooth devices on which you can normally enter a PIN so if this had been tested on any other device (eg mice, GPS, headsets etc) then the bug would have been immediately apparent.

There have been extensive changes to bluetooth in Intrepid which so far have had two major drawbacks (in addition to this bug, blueman no longer works at all and I like it a lot better than the built-in bluetooth utilities) and no advantages. I dare say that there was a good reason for the changes and I appreciate all the hard work that the devs have put into this, but the end result is a big step backward from Hardy.

lotus49 wrote:
> Same for me. I am trying to pair with a BT-Q880 GPS receiver and
> obviously, there is no way to enter a PIN so bluetooth in Intrepid is
> now useless for anything except keyboards.

I believe the latest snapshot of bluez-gnome adds support for some GPS receivers:
http://git.kernel.org/?p=bluetooth/bluez-gnome.git;a=commit;h=3db5bad47fafeebd8213fd85b8f47d2147d9250f

However, continually adding supported pin codes to the source code isn't really a long term solution. It would be better if there was an option to enter your own pin. Anyone know how to do this? I'm not familiar enough with gtk to feel comfortable adding this feature.

A possible catch-all patch (temporarily, at least), would be to change the default code tried from random to "0000," since it's what most devices use.

For example, from http://git.kernel.org/?p=bluetooth/bluez-gnome.git;a=tree
/bluez-gnome/wizard/main.c
----------CHANGE----------
line 548: target_pincode = g_strdup_printf("%d", g_random_int_range(1000, 9999));
-------------TO---------------
line 548: target_pincode = g_strdup_printf("%d", "0000");
-------------------------------
I'm not able to test this currently, can someone give it a try? I think the reason the number is randomly 1000-9999 is because leading zeros are not transferred correctly.

I can also confirm this bug.
Bluetooth Device: Bluemax Bluetooth GPS Receiver GPS-009
Bluetooth Applet 1.8
Linux hostname 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:06 UTC 2008 x86_64 GNU/Linux

I would need to type the PIN 0000, but it automatically generates a random PIN which fails.

me too, i can confirm it.
i cannot pair my bluetooth headset.I think a choice for the user either to choose a pin or let ubuntu generate one for him would be best.
Is there not a configuration file to disable automatic pairing and explicitly set a default pincode?

I'm having the same problem.

My bluetooth headset generates a random PIN code each time it is put in pairing mode (has an LCD display for track/volume/etc info).

Ubuntu is trying to pair with 0000 so fails.

Hobgoblin, I have the exact opposite. The bluetooth headset has a default of 0000 and has no screen displaying a random pin. Ubuntu generates a random pin and asks me to enter it to the device!!!!If it tried to pair with 0000 then i suppose the pairing would have succeeded!!!

Does anyone know if there is a way to use 0000 as default suggestion?

I'm having the same problem.

I am having the same problem with my Holex M0241.

When I try to pair under MacOS, a window comes up asking me to enter the PIN, I enter 0000 and it pairs without any problem.

Under Intrepid, a screen flashes up so quickly I can't see what it is saying, and then it says that pairing failed.

We need some way to enter the PIN under Intrepid.

I found a way to bypass this problem:

With "hcitool scan" I search for the MAC address of my device which should be paired. Then I browse its properties with "sdptool search SP 00:00:00:00:00:00" (replace 00:00:00:00:00:00 with the MAC address of the device which should be paired). While doing this the bluetooth-applet requests a user defined PIN for the device.

i confirm this problem with my:
1) bluetooth stereo headset Siemens HHB-750
2) Hp 995c bluetooth printer

@Dennis Heitmann

tried this way,but with no result

marek@ubuntu:~$ sdptool search SP 00:08:C6:66:2F:B8
Inquiring ...
Searching for SP on 00:08:C6:66:2F:B8 ...
Searching for SP on 00:1D:25:29:2F:F3 ...
Service Name: Serial Server
Service RecHandle: 0x10004
Service Class ID List:
  "Serial Port" (0x1101)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 4

Searching for SP on 00:05:16:42:88:62 ...
Service Name: Serial Port
Service RecHandle: 0x10000
Service Class ID List:
  "Serial Port" (0x00001101)
Protocol Descriptor List:
  "L2CAP" (0x00000100)
  "RFCOMM" (0x00000003)
    Channel: 1
Language Base Attr List:
  code_ISO639: 0x656e
  encoding: 0x6a
  base_offset: 0x100

Searching for SP on 00:13:D3:5D:4A:0C ...

and thats all from konsole

same for my HP 995c - blueototh printer

@trylink

Sorry. My idea seems not to be a general solution, but for my Bluetooth 56K V90 Modem (Trust) it is working like I said.

Perhaps "SP" is the wrong service. Try "sdptool search A2SNK xx:xx:xx:xx:xx:xx" for your bluetooth headset. Please read the manpage of sdptool or the manual of your device to figure out the proper service type/bluetooth profile. I'm at work so i cannot test Dennis Heitmanns solution for the problem.

I tried with my Holux M-241 and it gives this output:

wharvey@whnmacpro:~/Desktop$ sdptool search SP 00:1B:C1:04:F2:BB
Inquiring ...
Searching for SP on 00:1B:C1:04:F2:BB ...
Service Name: SPP Slave
Service RecHandle: 0x10000
Service Class ID List:
  "Serial Port" (0x1101)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 1
Language Base Attr List:
  code_ISO639: 0x656e
  encoding: 0x6a
  base_offset: 0x100

But no PIN request (same when running as sudo)

On Sat, Nov 8, 2008 at 6:27 AM, Jens Janssen <email address hidden> wrote:
> Perhaps "SP" is the wrong service. Try "sdptool search A2SNK
> xx:xx:xx:xx:xx:xx" for your bluetooth headset. Please read the manpage
> of sdptool or the manual of your device to figure out the proper service
> type/bluetooth profile. I'm at work so i cannot test Dennis Heitmanns
> solution for the problem.
>
> --
> bluetooth-wizard unable to pair headset
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

SOLVED!

At least for my A2DP audio sink (Nokia AD-42W).

1. Set up device in pairing-mode

2. "sudo sdptool browse" and then enter the bluetooth PIN code into the popup window.

OR

"sudo hcitool scan" to get the device id xx:xx:xx:xx:xx:xx
"sudo sdptool search --bdaddr xx:xx:xx:xx:xx:xx y" where y is your service type (in my case y=A2SNK).
Then enter the bluetooth PIN code into the popup window.

Finished.

For A2DP devices (Bluetooth Audio Devices):
Create ~/.asoundrc:
pcm.bluetooth {
 type bluetooth
        device xx:xx:xx:xx:xx:xx
        profile auto
}

If you are getting distorted sound output (e.g. when using a bluetooth mouse) then uncomment last three lines in /etc/bluetooth/audio.conf:
[A2DP]
SBCSources=1
MPEG12Sources=0

Same problem here with Intrepid 8.10 on a Sony Vaio VGN-TX770P trying to pair with a Telenav BT-339 GPS receiver.

The GPS receiver paired with my Psion Tungsten, so I know it works, using PIN 0000.

Gnome Bluetooth applet does not let me enter a PIN for a device whose PIN is preset and cannot be changed.

I tried the workarounds suggested here, and get no joy...
Please fix the Bluetooth applet to allow user to enter a PIN.

K.

Okay, I have a partial patch for this problem. You need to download the source code and change a line of code. I say a partial patch because you need to recompile and install any time you want to change the default PIN code.

In the source code, change the line near the bottom in /wizard/main.c
-----------FROM-----------
target_pincode = g_strdup_printf("%d", g_random_int_range(1000, 9999));
-------------TO-------------
target_pincode = g_strdup_printf("0000");
-----------------------------

You can change the "0000" part to whatever your PIN number is. I am not a programmer, but I tried this and was able to connect to my device.

>I personally think the solution to this bug should be to offer a few options right after you do the device select screen. They
>should be preselected depending on the device you are using.

>(1) Randomly chosen PIN number that you enter on the device (Good for keyboards)
>(2) Preselected common PIN number (Typically 0000 or 1234, show in the UI)
>(3) Enter a PIN number

Why make it so complicated ? Just let the user enter whatever pin he wants (3) like it was perfectly working before (you could prefill the field with some random PIN however, so that users who don't know what a pin is and are not using devices who need specific pins could just hit next)...

I have the same problem, but sometimes devices can ignore pairing.

I have two serial devices (GPS and OBD), one uses 0000, the other 1234.

I can't use the wizard. Perhaps someone can patch it to read a file from /etc/bluetooth/pin or something.

They need to have a way to enter your own PIN instead of selecting one randomly, or at least have it read from a configuration file or something.

This seems to be an upstream issue, so I filed this in gnome bugzilla. Let's see what people say there: http://bugzilla.gnome.org/show_bug.cgi?id=560316

The package with the wayward wizard is bluez-gnome, but apparently there is a "agent" so the pincode selection should be pluggable (i.e. some config file should be able to point to something which will ask). I patched it to read from /tmp/wizardpincode if that file exists and was able to get it to pair.

I can't get sound out of my headset yet, but it does see it.

I must say I find the upstream reaction rather less helpful and optimal. (http://bugzilla.gnome.org/show_bug.cgi?id=560315#c5)

bluez-gnome seems to intent to special case each non-keyboard device in their source code rather than just allowing people to enter a fixed PIN in the wizard. Hardcoding the stuff is bound to lag behind existing devices and seems a rather bloaty solution to me. Most of the time people would know best whether to use 1234 or 0000 or somesuch. Whatever.

As a consequence, I stop caring about upstream and work around this with a custom shell script.

I wrote a followup - a web page for every owner of a bluetooth device
that needs a special PIN that would submit it as a new bug report is
possible...

Perhaps Ubuntu can write its own patch - it looks simple enough but I
would need time to add the panel (I've only done Gtk in Python).

The short answer is it cannot be hardcoded which is why every other
implementation (e.g. my Nokia tablet, or even my phone) doesn't do so.
 They typicall present something random but editable.

On Tue, Nov 11, 2008 at 8:23 AM, spaetz <email address hidden> wrote:
> I must say I find the upstream reaction rather less helpful and optimal.
> (http://bugzilla.gnome.org/show_bug.cgi?id=560315#c5)
>
> bluez-gnome seems to intent to special case each non-keyboard device in
> their source code rather than just allowing people to enter a fixed PIN
> in the wizard. Hardcoding the stuff is bound to lag behind existing
> devices and seems a rather bloaty solution to me. Most of the time
> people would know best whether to use 1234 or 0000 or somesuch.
> Whatever.
>
> As a consequence, I stop caring about upstream and work around this with
> a custom shell script.
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

CC-ed from the relevant bug discussion. This is my first GTK program
(at least the original modal dialog), so it is probably horrid, but
solves the problem. I don't know how to integrate it with the wizard
gtk objects (it would require either a new PIN selection page, or
something in the existing page adding a text entry to the label and
something to pause it until something was clicked). It also needs
checking and verification/validation added. If it was in PyGtk I'd do
better.

diff -Bbur bluez-gnome-1.8/wizard/main.c bluez-gnome-1.8-tz/wizard/main.c
--- bluez-gnome-1.8/wizard/main.c 2008-10-04 14:32:56.000000000 -0500
+++ bluez-gnome-1.8-tz/wizard/main.c 2008-11-11 10:54:13.000000000 -0600
@@ -56,6 +56,34 @@

 static GtkTreeSelection *search_selection = NULL;

+static GtkWidget *pinentry, *pindialog;
+static char usepincode[32];
+void clicked()
+{
+ char *text;
+
+ text = gtk_entry_get_text( GTK_ENTRY(pinentry));
+ strcpy( usepincode, text );
+ gtk_widget_destroy( pindialog );
+}
+
+static void run_pin_dialog()
+{
+ GtkWidget *label, *button;
+
+ pindialog = gtk_dialog_new();
+ label = gtk_label_new ("Passkey for Pairing");
+ pinentry = gtk_entry_new ();
+ gtk_entry_set_text( GTK_ENTRY(pinentry),target_pincode );
+ button = gtk_button_new_with_label("Pair");
+ gtk_signal_connect_object(GTK_OBJECT (button), "clicked", clicked , NULL);
+ gtk_container_add (GTK_CONTAINER
(GTK_DIALOG(pindialog)->action_area), button);
+ gtk_container_add (GTK_CONTAINER (GTK_DIALOG(pindialog)->vbox), label);
+ gtk_container_add (GTK_CONTAINER (GTK_DIALOG(pindialog)->vbox), pinentry);
+ gtk_widget_show_all (pindialog);
+ gtk_dialog_run( GTK_DIALOG(pindialog) );
+}
+
 static gboolean pincode_callback(DBusGMethodInvocation *context,
      DBusGProxy *device, gpointer user_data)
 {
@@ -72,12 +100,19 @@
     target_type == BLUETOOTH_TYPE_HEADPHONE)
   pincode = "0000";

+
+ target_pincode = pincode;
+
+ strcpy( usepincode, pincode );
+
+ run_pin_dialog();
+
  text = g_strdup_printf(_("Please enter the following PIN code: %s"),
- pincode);
+ usepincode);
  gtk_label_set_markup(GTK_LABEL(label_passkey), text);
  g_free(text);

- dbus_g_method_return(context, pincode);
+ dbus_g_method_return(context, usepincode);

  return TRUE;
 }

On Tue, Nov 11, 2008 at 9:11 AM, tz <email address hidden> wrote:
> I wrote a followup - a web page for every owner of a bluetooth device
> that needs a special PIN that would submit it as a new bug report is
> possible...
>
> Perhaps Ubuntu can write its own patch - it looks simple enough but I
> would need time to add the panel (I've only done Gtk in Python).
>
> The short answer is it cannot be hardcoded which is why every other
> implementation (e.g. my Nokia tablet, or even my phone) doesn't do so.
> They typicall present something random but editable.
>
> On Tue, Nov 11, 2008 at 8:23 AM, spaetz <email address hidden> wrote:
>> I must say I find the upstream reaction rather less helpful and optimal.
>> (http://bugzilla.gnome.org/show_bug.cgi?id=560315#c5)
>>
>> bluez-gnome seems to intent to special case each non-keyboard device in
>> their source code rather than just allowing people to enter a fixed PIN...

I can confirm this.
It's very anoying, i got my BT keyboard today
Also i like to use my BT Headset (I hoped for pulseaudio 9.13) but this is less important
I already had paired my mobile phone successfully, but after deleting it from my known devices the wizard doesn't ask or doesn't tell me a PIN anymore
I hope this will be changed soon, else i will reinstall hardy

I've attached the above as a patch to this message

Tecom headsets use 1111, not 0000 or 1234.
http://www.tecom.com.sg/bt3061ausermanual.html

I was able to used the patched version to pair everything I've thrown at it so far.

Perhaps someone who is adept at Gtk+ could rewrite it properly

For better security the default random passcode should be 8 bytes (the spec allows up to 16).

The entry text area should be limited to numbers and perhaps a larger font, and localization might be a good idea, and the labels and button might have better descriptive text. Also check I didn't leave in a memory leak since I'm not sure what gets deallocated automatically.

For known device problems:

If you delete the device from the list, it should ask for a pin the next time, but you might need to exit the wizard and/or preferences and restart the process. This has worked for me.

Also some devices don't require passcodes so will pair without them, or worse, the bluetooth subsystem "remembers" the WRONG details (I had a similar problem on my Nokia tablet - a headset wouldn't connect though was paired and deleted and re-paired several times)

You would need to find and manually delete any entries from /var/lib/bluetooth/(adapteraddress)/* referring to the device, or stop bluetooth, wipe all the entries in the directory and re-pair (pun intended) everything, and restart the bluetooth system.

I can't easily duplicate the problem but if it happens, I'll try to find the entry that needs to be deleted. Somewhere in the bluez stack, if a device is deleted, it needs to be purged (all references removed) or at least a purge option should be given. Or perhaps purge all unpaired devices or something similar, but there may be a simpler fix.

Also, could we bump the importance of this bug to major or higher?

It is currently impossible (not using complex hackage in the terminal or a patch like I wrote) to pair any device with a fixed bluetooth address. Well, maybe not impossible, but 1 in 10k are not good odds.

This defeats the purpose of the intrepid upgrade to the bluetooth, since you could pair devices under hardy, and a very large number of things which you would want to use bluetooth on are peripherals with fixed passcodes.

Its a problem with Linux kernel that comes with intrepid. I installed the kernel from hardy's alternate disk and everything worked as before.

No, I don't think it's a kernel problem. Just to be sure I just tested with my old Hardy kernel (2.6.24-21), and as expected, the bug stil occured (got a randomly selected PIN to enter on my keyboardless GPS).

And as you can see from the discussion and gnome bugzilla, the buggy behaviour is deliberate and is considered a feature by the developer...

(Btw, note that the bug has been closed on gnome bugzilla since the author of the bug didn't have the exact headset mentioned in the title.)

The patch works. I don't know if anyone wants to get it into an Ubuntu update.

On Wed, Nov 12, 2008 at 12:58 PM, matli <email address hidden> wrote:
> No, I don't think it's a kernel problem. Just to be sure I just tested
> with my old Hardy kernel (2.6.24-21), and as expected, the bug stil
> occured (got a randomly selected PIN to enter on my keyboardless GPS).

It is not in the kernel. There may be a way of plugging the bluetooth
agent within the wizard, but it uses g_random_int (around line 550) to
select a random pincode and only overrides it for certain devices with
an inline hardcoded blacklist. The bluetooth system has a callback to
get the pin (expecting a dbus message with the desired pincode in
response), and that is where the fix must occur - modifying the
pincode BEFORE the dbus message is sent. That is where my patch
intercepts the random number and lets it be changed. If no pairing is
required I don't think the callback will occur at all. And this
callback setup is in the bluez stack which should not have changed
significantly between hardy and intrepid.

I'm using a 64 bit setup, but could put a binary (and a 32 bit
version) up somewhere of my patched version for those who can't or
don't want to compile.

> And as you can see from the discussion and gnome bugzilla, the buggy
> behaviour is deliberate and is considered a feature by the developer...

Or as he says, devices which aren't easily identifiable or
classifiable as having a fixed pincode are "crappy" so he doesn't want
to bother with them even if they might be large in number and things
the users will often want to pair like
headsets/handsfree/speakerphones and GPS units. Nor are there legal
or technical reasons preventing them from working using a
user-modifiable pincode (which every other implementation I have seen
has in one way or another. And as far as I know in the bluetooth
spec, nothing specifies how the PINs are arrived at. Worse, for
security longer PINs should be used and his default is fixed to four
digits (The Mac uses 8 when it randomly selects a PIN) and I can't
even do that.

I deal in embedded with things in ROM chips that actually break
longstanding specs, and I can't just say "I won't support X". This is
much less serious.

> (Btw, note that the bug has been closed on gnome bugzilla since the
> author of the bug didn't have the exact headset mentioned in the title.)

Perhaps I should go through all my devices and submit individual bug
reports for those which wouldn't have paired without my patch as he
apparently wanted me to.

More variations (alas without the BT addr ranges):

http://www.bb-shopping.com/Pama-Bluetooth-Car-Kits-and-Headset-Pairing-Codes.html

@malti
@tz
but without the kernel of hardy it would simply give me connection error instead of giving me a pin code to type.

@tz
Add your patch as an attachment and not inline (it's breaking the format of the patch) and I'll add it to my PPA.

What is the address of your PPA?

I would like to try this with my gps reciever.

Thanks

Wilbur

On Wed, Nov 12, 2008 at 10:34 AM, Adilson Oliveira <email address hidden> wrote:
> @tz
> Add your patch as an attachment and not inline (it's breaking the format of the patch) and I'll add it to my PPA.
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

It is quite clear the developer is behaving decidedly irrationally (not to mention aggressively) on this one and is insisting, for reasons best known to himself, that users should not be permitted to enter their own PIN and each device's hard-coded PIN should be hard-coded into the source. His argument that users will pick insecure PINs is akin to suggesting users should not be able to pick their own passwords and instead should have their 10 digit alphanumeric password chosen for them whether they like it or not.

I have to say that this is bizarre. It worked fine and now it is broken. His view is that each piece of hardware that will not pair is a separate bug. I think we should therefore humour him (after all he has done the hard work here even if he does have bizarre views) and file a separate bug for each and every piece of hardware that will not pair.

The upshot of this is that every downstream distro will have to address this issue separately as I don't believe that anyone will share his view. Consequently we shall eventually end up with the solution that the users want and he doesn't but it will involve much more work for everyone, including him.

Perhaps if thirty bugs are reported, he may come to his senses but I doubt it. He will probably come here and threaten to have me kicked from LaunchPad instead - that seems to be more his style.

Original patch was in message 37 after I realized that inlining was bad and that the web page allowed attachments:

https://bugs.launchpad.net/ubuntu/+source/bluez-gnome/+bug/284994/comments/37

Here is an update with the field width set to 16, and removal of the 0000 hacks since many headsets use something else anyway.

(Now if I or someone else can figure out how to get GTK to limit input to numeric... Spinboxes don't allow 0000 v.s. 000000 - it must be text, but only numbers though I could validate and retry - I also don't handle closing quite right, but this gets the PIN into an editable field)

@tz
Thanks, I missed this message. Anyway, I just tested locally and works fine. Just sent to my PPA here https://edge.launchpad.net/~agoliveira/+archive so should be ready to use in a few minutes.
tz, I also missed to add your information regarding the patch. As soon as others confirm it works, I'll catch the file again, give it some polishing and see what I can do to have it added to Intrepid or, worse case scenario, Jaunty.

@Ravi

The bluez stack might be slightly updated. There are some (insecure) devices that will connect without any PIN but allow one optionally, sometimes the fixed values - GPS and serial devices often do this. I suspect that the stack changed to invoke the callback in all cases now and there is some way of saying "no pin" using it (e.g. a zero length string return, or NULL) though I haven't looked through the code.

So it might have worked because your device worked in a PINless mode. It would help if you could verify this. If it connects without any PIN being entered, it doesn't need one.

I will have to try it too - I think my GPS units will also work PINless.

@lotus49

As I noted, Pins can be up to 16 digits, and I've noted Apple uses 8 digits (The Nokia internet tablet uses 4, most phones pick 4 but accept more). If security was a concern a longer PIN should be used, so it is irrational to force PINs that are both random and short.

Perhaps adding more text to my dialog would help, e.g. "Bluetooth security requires having a random pincode which is provided below, however if your device requires a specific pincode, change the value it to the one your device needs, or if you desire more security, add more digits".

I've been dealing with Bluetooth devices for a while and if there were a few isolated "crappy devices" I would probably rethink how it should be done, but over 1/2 of the BT devices I have won't work with the current setup. I could file at least a half-dozen separate bugs right now requesting special casing, and the more I look the more special cases for both devices and PINs I find. Thirty bugs? I think I said thousands, but there would probably be hundreds just from the people on the various lists experiencing the problem.

My patch is only alpha quality (any Gtk+ wizard should be able to fix it to release quality in a very short time), but even as-is you can at least enter a fixed PIN and use your device as soon as it gets packaged and you can get the update. His approach? Daily builds just to get the latest growing list of special cases? Or devices that won't work for another few weeks or months?

The upstream developers apparently have no clue what users want. This fixed pin per device "solution" does not help at all. There are bluetooth devices which give you a (at least pseudo-) random pin depending on the serial no of the device.
In this case a device/pin database does not help.

@Adilson Oliveira
@tz

Thank you very much!! You guys saved my day! and the ppa prevented me from killing myself :)
I just got my new bt keybord, to find me not beeing able to pair it ..

I hope the bluez-gnome devs will change this behavior of the wizard soon.

@Daniel Newman
Could you please provide the output of :

1) hcitool scan
2) hcitool inq [bluetooth address]

And

3) tell us the correct pin for your device

And attach it here or directly in the upstream bug ?

http://bugzilla.gnome.org/show_bug.cgi?id=560315#c2

@Others
If you have other devices that are affected by this bug, could you please attach the same informations (1,2 and 3) here and/or open a new bug upstream (I will do it for you if you don't have a gnome account).

Jonathan, the upstream bug you pointed seems to be closed. Also, I don't see why hardcode every single device unless you leave an option for something like tz's patch. Maybe first try to figure out what device is and, if it's not possible, open a dialog to enter the pin code manually.

Adilson, I completely agree with you. However I think we should provide the upstream developer with the infos he requested (the bug has been closed by the reporter as he doesn't own the mentioned device, but it can be reoppened).

He'll see whether the situation is maintainable in the long term or not. If he can fix his automatic detection algorithm for most/all devices this will show that his choice was good, if he cannot (which I guess is likely to happen), he'll might reconsider his approach. In both cases the end users will have a better situation than now.

On the other hand if we don't provide him with the requested infos, we'll appear as whiners.

hcitool scan
Scanning ...
    [bdaddr] X3 micro

hcitool inq [bdaddr]
Inquiring ...
    [bdaddr] clock offset: 0x39fc class: 0x200404

The correct pin is 1234.

Jonathan Ernst wrote:
> @Daniel Newman
> Could you please provide the output of :
>
> 1) hcitool scan
> 2) hcitool inq [bluetooth address]
>
> And
>
> 3) tell us the correct pin for your device
>
> And attach it here or directly in the upstream bug ?
>
> http://bugzilla.gnome.org/show_bug.cgi?id=560315#c2
>
> @Others
> If you have other devices that are affected by this bug, could you please attach the same informations (1,2 and 3) here and/or open a new bug upstream (I will do it for you if you don't have a gnome account).
>
>

Okay, here is the thread with the response from a developer on the bluetooth-linux mailing list:
http://article.gmane.org/gmane.linux.bluez.kernel/721

>I didn't say it was a bad idea to allow users to enter a fixed PIN, I
>said it would be a bad idea to replace random PINs altogether with
>user-provided PINs.

With a legitimate concern

>That wouldn't work, a lot of devices will get out of pairing mode after
>an unsuccesful pairing.

And offers a good solution

>My solution would be to have a button at the bottom of the device
>selection page called "PIN options" (or similar).

The bug has been closed by the original submitter (http://bugzilla.gnome.org/show_bug.cgi?id=560315#c14) , so it would probably be better to open a new bug.

Ok then. There you have it the first one. It's a GPS Holux 1000B

adilson@cartman:~$ hcitool scan --refresh
Scanning ...
 XX:XX:XX:XX:XX:XX HOLUX_M-1000
adilson@cartman:~$ hcitool inq XX:XX:XX:XX:XX:XX
Inquiring ...
 XX:XX:XX:XX:XX:XX clock offset: 0x77bd class: 0x001f00

The second one is a headphone Acoustic Research ARWH1
adilson@cartman:~$ hcitool scan
Scanning ...
 XX:XX:XX:XX:XX:XX ARWH1

adilson@cartman:~$ hcitool inq XX:XX:XX:XX:XX:XX
Inquiring ...
 XX:XX:XX:XX:XX:XX clock offset: 0x3e14 class: 0x08010c
 XX:XX:XX:XX:XX:XX clock offset: 0x4f55 class: 0x240404

@tz

i have a nokia 7610 phone. With the kernel in Heron if I tried to pair it up it simply gives error as connection error at both sides. Means if phone initiates pairing it gets connection error and if pc initiates pairing it gets the connection error too. The file transfer which Nokia 7610 supports without pairing failed too.

Now when I used the older kernel supplied with Hardy I could do the pairing and transfer the files too.

I tried this from the ppa and it worked fine with my Holux m-241.

Thank you very much.

On Wed, Nov 12, 2008 at 11:25 AM, Adilson Oliveira <email address hidden> wrote:
> @tz
> Thanks, I missed this message. Anyway, I just tested locally and works fine. Just sent to my PPA here https://edge.launchpad.net/~agoliveira/+archive so should be ready to use in a few minutes.
> tz, I also missed to add your information regarding the patch. As soon as others confirm it works, I'll catch the file again, give it some polishing and see what I can do to have it added to Intrepid or, worse case scenario, Jaunty.
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

@Adilson
Thanks for your input, I'll report those devices as soon as you give me #3 a.k.a. "tell us the correct pin for your device"

@Wilbur
Could you please post :
1) hcitool scan
2) hcitool inq [bluetooth address]

And

3) tell us the correct pin for your device

Thanks again

@Hobgoblin
Your device is a very interesting test case to show that the approach adopted upstream cannot work (the one which generate random pins). Could you please give me the requested informations :

1) hcitool scan
2) hcitool inq [bluetooth address]
3) The model of your device

@lotus49
@Conehead77
I also need these informations for your GPS device

Thanks

@Adilson and others
Please don't hide at least the first three hex digit of your devices as it is needed by upstream developpers. (please give me those digits)

@Adilson
> 2)adilson@cartman:~$ hcitool inq XX:XX:XX:XX:XX:XX
> Inquiring ...
> XX:XX:XX:XX:XX:XX clock offset: 0x3e14 class: 0x08010c
> XX:XX:XX:XX:XX:XX clock offset: 0x4f55 class: 0x240404

Please tell me which of those two results correspond to the ARWH1 device ?

without the pin entering version of bluez-gnome from https://edge.launchpad.net/~agoliveira/+archive my headset would also not pair also it has default pin "0000".

Formerly, I was able to trigger pin input request from bluetooth-applet via this command:

$ sudo hcitool cc <btaddress>

type of headset HBH-PV700.

$ hcitool inq
00:12:EE:XX:XX:XX clock offset: 0x0cf7 class: 0x200404

Again, pairing legacy worked with the ppa version of bluez-gnome.

@ravi:

I assume you meant "With the kernel in Intrepid", not (hardy) Heron.

This might be a separate bug (from the fixed pin problem). If so it
might be better to start a new bug report (and post the number here),
but for now...

Could you try from a intrepid live CD (I'm worried that the
mix-and-match might be a cause)? And I assume your phone allows for
any number to be used as the PIN (i.e. if linux picks 2468, you can
type 2468 on the phone), or initiate pairing from the phone?

On Wed, Nov 12, 2008 at 11:52 PM, Ravi <email address hidden> wrote:
> @tz
>
> i have a nokia 7610 phone. With the kernel in Heron if I tried to pair
> it up it simply gives error as connection error at both sides. Means if
> phone initiates pairing it gets connection error and if pc initiates
> pairing it gets the connection error too. The file transfer which Nokia
> 7610 supports without pairing failed too.
>
> Now when I used the older kernel supplied with Hardy I could do the
> pairing and transfer the files too.
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

And what my patch does is to display the randomly generated PIN (and
most devices will accept longer, more secure ones - 8 is a typical
number). I never suggested replacing them altogether.

The user can leave the random PIN and use it or modify it.

I knew about the paring fail exits problem which is why I didn't
suggest a retry (or series thereof).

And I think I suggested pin options very early in the discussions (the
wizard would have to add another page for it which is a bit beyond my
limited Gtk+ skills and time budget, and there was nothing in the
program for a user entry field - the pin was part of a label, not an
entry (spinboxes having the problem of how do you represent N digits
of zeros) and there was no place to change it before the get pin
callback - which is where I added the modal dialog ).

My patch unbreaks intrepid (and any others using the wizard) for the
short term, and I'll let the more experienced gnomes write something
cleaner, but it will require a lot of UI rewiring.

On Wed, Nov 12, 2008 at 8:52 PM, DanielRoesler <email address hidden> wrote:
> Okay, here is the thread with the response from a developer on the bluetooth-linux mailing list:
> http://article.gmane.org/gmane.linux.bluez.kernel/721
>
>>I didn't say it was a bad idea to allow users to enter a fixed PIN, I
>>said it would be a bad idea to replace random PINs altogether with
>>user-provided PINs.
>
> With a legitimate concern
>
>>That wouldn't work, a lot of devices will get out of pairing mode after
>>an unsuccesful pairing.
>
> And offers a good solution
>
>>My solution would be to have a button at the bottom of the device
>>selection page called "PIN options" (or similar).
>
> The bug has been closed by the original submitter
> (http://bugzilla.gnome.org/show_bug.cgi?id=560315#c14) , so it would
> probably be better to open a new bug.
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Here are the results for my Holux M-241

wharvey@whnmacpro:~/Desktop$ hcitool scan
Scanning ...
 00:1B:C1:04:F2:BB HOLUX_M-241
wharvey@whnmacpro:~/Desktop$ hcitool inq 00:1B:C1:04:F2:BB
Inquiring ...
 00:1B:C1:04:F2:BB clock offset: 0x1c6d class: 0x001f00
wharvey@whnmacpro:~/Desktop$

Wilbur

On Wed, Nov 12, 2008 at 11:01 PM, Jonathan Ernst
<email address hidden> wrote:
> @Hobgoblin
> Your device is a very interesting test case to show that the approach adopted upstream cannot work (the one which generate random pins). Could you please give me the requested informations :
>
> 1) hcitool scan
> 2) hcitool inq [bluetooth address]
> 3) The model of your device
>
> @lotus49
> @Conehead77
> I also need these informations for your GPS device
>
> Thanks
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Got the same Problem with my Navigon Triceiver (made by GNS):

thomas@augustus:/etc/bluetooth$ hcitool scan
Scanning ...
 00:0B:24:44:FC:08 Triceiver
thomas@augustus:/etc/bluetooth$ hcitool inq 00:0B:24:44:FC:08
Inquiring ...
 00:0B:24:44:FC:08 clock offset: 0x334e class: 0x001f00

I don't quite know the standard pin (i think it's something like 1234 or 0000)...

I hope this bug is fixed soon...

Tominator, check the device docs for the standard pin and use the blues-package from my PPA as explained above. It will allow you to enter the pin manually then you can pair your device.

OK here you are Jonathan. This is the information you requested for my
Qstarz BT-Q880 GPS receiver.

$ hcitool scan
Scanning ...
    00:00:00:00:46:7C BT-Q880
$ hcitool inq 00:00:00:00:46:7C
Inquiring ...
    00:00:00:00:46:7C clock offset: 0x7c58 class: 0x000000

The default PIN for this is 0000.

Thanks for stepping in and offering to collate this information Jonathan -
it's very helpful.

lotus49

2008/11/13 Jonathan Ernst <email address hidden>

> @Hobgoblin
> Your device is a very interesting test case to show that the approach
> adopted upstream cannot work (the one which generate random pins). Could you
> please give me the requested informations :
>
> 1) hcitool scan
> 2) hcitool inq [bluetooth address]
> 3) The model of your device
>
> @lotus49
> @Conehead77
> I also need these informations for your GPS device
>
> Thanks
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "bluez-gnome" source package in Ubuntu: Confirmed
>
> 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 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.
>

Here is the current upstream related bug list :

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 NEEDINFO!
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

Dennis Heitmann, Adilson Oliveira and Hobgoblin, would you mind giving the requested infos ?

@tekknokrat
They need hcitool scan output for your HBH-PV700, not hcitool cc

Thanks in advance.

My problem related:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/296358
In this case it's a printer Hp Photosmart D5160.

Information requested added to the upstream bugs.

@Jonathan Ernst

1) hcitool scan

XX:XX:XX:XX:XX:XX Bluetooth Modem - Serial No. 106773

2) hcitool inq [bluetooth address]

XX:XX:XX:XX:XX:XX clock offset: 0x04b5 class: 0x420210

3) The model of your device

Trust V92 56K Bluetooth Wireless Modem

The dirty half-dozen:

00:03:89:C4:30:8B clock offset: 0x3c73class: 0x240404 260Plantronics PIN 0000
00:0A:94:04:FE:95 clock offset: 0x4bc5class: 0x20040c VS600 headset pin 0000
00:03:C9:30:97:64 clock offset: 0x0217class: 0x200404 Tecom ("BT
Headset") headset pin 1111
00:06:66:01:45:C3 clock offset: 0x0d60class: 0x001f00 OBDPros scantool pin 1234
00:0B:0D:88:E6:DC clock offset: 0x741fclass: 0x001f00 G-Rays1 (gps) pin 0000
00:0A:3A:25:A2:A7 clock offset: 0x6431class: 0x001f00 HUDGPS pin 0000

The GPS units and the Tecom and OBDPros are definitely candidates.

On Thu, Nov 13, 2008 at 5:20 PM, Jonathan Ernst <email address hidden> wrote:
> Here is the current upstream related bug list :
>
> 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 NEEDINFO!
> 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
>
> Dennis Heitmann, Adilson Oliveira and Hobgoblin, would you mind giving
> the requested infos ?
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

@Dennis Heitmann
1) Please don't hide the first three hex digits of your bluetooth devices, they are needed by upstream
2) What is the pin of your device, you said it was 0000 but according to http://osdir.com/ml/linux.bluez.user/2004-09/msg00138.html the pin might be a 12 digits pin printed at the bottom of the modem

@tz
could you provide the upstream required infos for those devices if they are affected by this bug, thanks

@Jonathan Ernst

Right, the PIN is printed on the back of the modem and is 12 digits long.

1) hcitool scan

00:0C:55:XX:XX:XX Bluetooth Modem - Serial No. 106773

2) hcitool inq [bluetooth address]

00:0C:55:XX:XX:XX clock offset: 0x04b5 class: 0x420210

3) The model of your device

Trust V92 56K Bluetooth Wireless Modem

@tz
>could you provide the upstream required infos for those devices if they are affected by this bug, thanks
> "The GPS units and the Tecom and OBDPros are definitely candidates."

I meant, can you confirm that all those devices are affected by this bug ?

@Jonathan Ernst

Sony Ericsson Headset

$ hcitool scan
Scanning ...
 00:12:EE:XX:XX:XX HBH-PV700

$ hcitool inq
Inquiring ...
 00:12:EE:XX:XX:XX clock offset: 0x2f7e class: 0x200404

All of the following I confirmed (and with the exception of the last
one were confirmed before I wrote the patch because I couldn't pair
them at all).

Note I have two GRays-1, neither would pair. I also have a second
Tecom, which I didn't bother trying (since it would be the same)

00:03:C9:30:97:64 clock offset: 0x0217class: 0x200404 Tecom ("BT
Headset") headset pin 1111
00:06:66:01:45:C3 clock offset: 0x0d60class: 0x001f00 OBDPros scantool pin 1234
00:0B:0D:88:E6:DC clock offset: 0x741fclass: 0x001f00 G-Rays1 (gps) pin 0000
00:0A:3A:25:A2:A7 clock offset: 0x6431class: 0x001f00 HUDGPS pin 0000

On Fri, Nov 14, 2008 at 4:25 AM, Jonathan Ernst <email address hidden> wrote:
> @tz
>>could you provide the upstream required infos for those devices if they are affected by this bug, thanks
>> "The GPS units and the Tecom and OBDPros are definitely candidates."
>
> I meant, can you confirm that all those devices are affected by this bug
> ?
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

To clarify:

Addr | Class | BT hcitool scan name | PIN
00:03:C9:30:97:64 | 0x200404 | BT Headset | 1111
00:06:66:01:45:C3 | 0x001f00 | OBDPros scantool | 1234
00:0B:0D:88:E6:DC | 0x001f00 | G-Rays1 | 0000
00:0A:3A:25:A2:A7 | 0x001f00 | HUDGPS | 0000

Another one...

$ hcitool scan
Scanning ...
 00:0C:78:xx:xx:xx Philips SHB7100
$ hcitool inq 00:0C:78:xx:xx:xx
Inquiring ...
 00:0C:78:42:xx:xx clock offset: 0x14f5 class: 0x24040c

Philips Bluetooth Stereo Headset SHB7100
Pin is: 0000

Philips Bluetooth Stereo Headset SHB7100 with default pincode 0000 also can not be paired with Ubuntu 8.10.
(only the clock offset seems to be different between my SHB6100 and the SHB7100)

$ hcitool scan
Scanning ...
 00:0C:78:xx:xx:xx Philips SHB6100
$ hcitool inq 00:0C:78:xx:xx:xx
Inquiring ...
 00:0C:78:xx:xx:xx clock offset: 0x6305 class: 0x24040c

I've made a quick patch for the wizard so it has a checkbutton for overriding de pin with "0000".

Just download the source of bluez-gnome:
apt-get source bluez-gnome

Go to the source path of the wizard:
cd bluez-gnome-1.8/wizard

Copy gpshack.diff to here and apply the patch
patch main.c < gpshack.diff

Configure and build everything, but only install the wizard
cd ..
./configure
make
cd wizard
sudo make install

If everything goes fine, you now can choose to use "0000" as pin.
This is however a pretty dirty hack, I take no responsibilities for any damage done by this patched version(or the patch itself)

The problem is many devices use pins other than 0000 - I have two that
use 1111 and 1234.

My patch pops up a confirmation box. Perhaps you could merge it with
yours so the dialog would pop up only if you checked the box.

On Sat, Nov 22, 2008 at 8:43 AM, CADE20 <email address hidden> wrote:
> I've made a quick patch for the wizard so it has a checkbutton for
> overriding de pin with "0000".
>
> Just download the source of bluez-gnome:
> apt-get source bluez-gnome
>
> Go to the source path of the wizard:
> cd bluez-gnome-1.8/wizard
>
> Copy gpshack.diff to here and apply the patch
> patch main.c < gpshack.diff
>
> Configure and build everything, but only install the wizard
> cd ..
> ./configure
> make
> cd wizard
> sudo make install
>
> If everything goes fine, you now can choose to use "0000" as pin.
> This is however a pretty dirty hack, I take no responsibilities for any damage done by this patched version(or the patch itself)
>
> ** Attachment added: "Patch for bluez-gnome-1.8/wizard/main.c"
> http://launchpadlibrarian.net/19860209/gpshack.diff
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I modified my patch, I've added a textbox for choosing any pincode.

I still take no responsibility for any damage done.

I just upgraded to Ubuntu 8.10 (Intrepid Ibex w/Gnome) and had similar problems with my Bluetooth Sony speaker (unable to pair with this device which has a hardcoded pincode). The problem is that the Gnome Bluetooth applet generates a random pincode and the Sony speaker has no way to respond to this pincode as it doesn't have a built-in keypad.

PROBLEM SOLVED! -- Just now I came across this page (http://www.technetra.com/2008/11/22/pairing-stubborn-bluetooth-devices-in-fedora-10-ubuntu-ibex/) -- which provides a script using DBus commands to pair Bluetooth devices. I tried it on my Ubuntu Ibex system and it worked for me. I'm now able to pair my Sony speaker and use Rhythmbox.

HTH
Cheers

CADE20 wrote:
> I modified my patch, I've added a textbox for choosing any pincode.

Please see the upstream dev discussion on how the bluez developer would
solve the issue in a way that seems reasonable:
http://thread.gmane.org/gmane.linux.bluez.kernel/717/focus=721

Such a patch should be done according to that and submitted upstream, to
solve this the correct way once and for all.

That sounds like a good idea provided:

1. Pincodes are specified to be as long as 16 digits. If you are
going to bother with a random pin, it should be 8 digits by default if
security is not to be just a lesser joke. Apple uses 8. If you have
a PIN entry box, it should allow a max of 16 digits.

2. GTK Text areas (unless I've missed something) allow for non-numeric
entry. The spinboxes are pure numeric so there is no way to do
00000000 v.s. 0000. Something should validate or limit user input to
the 10 numeric digits. This should be done before the patch goes into
the main codebase.

3. The format is good (later in the message):

If Pin is required:
(*) Enter PIN of RRRRRRRR on Device
( ) Device specifies PIN of [0000____________]

(radiobutton, not checkbox)

-----------------
On Mon, Nov 24, 2008 at 8:24 AM, spaetz <email address hidden> wrote:
> CADE20 wrote:
>> I modified my patch, I've added a textbox for choosing any pincode.
>
> Please see the upstream dev discussion on how the bluez developer would
> solve the issue in a way that seems reasonable:
> http://thread.gmane.org/gmane.linux.bluez.kernel/717/focus=721
>
> Such a patch should be done according to that and submitted upstream, to
> solve this the correct way once and for all.
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Hello

I have found a temporarily solution for pairing keyboard less device like GPS unit.

1) First operations is finding the GPS device address with this command:

hcitool scan
Scanning ...

 00:13:F1:01:40:AE BT-GPS 0140AE

 00:18:8D:11:5F:F3 Zinux6680

Record the BT-GPS address, this is used later.

2) Enable the authentication on the pc blue-tooth dongle.

sudo hciconfig hci0 auth

3)Create a connection with the device
sudo hcitool cc 00:13:F1:01:40:AE

Now a popup menu request the pin for the device, insert it.

Now if you right click on the blue-tooth-applet and select preferences you see the GPS paired.

Good luck.

That's brilliant, Roberto. The simple answers are always the best.

Roberto. The same solution works in fedora distribution.

I've paired up the headset with my notebook, I believe.(please see the picture)

However, how can I ouput the sound to the BT headset ??
Thank you !

Ciao,

Yes, you have correctly paired the headset, but i can't help how to
use it.
I do not have experience with bluetooth sound device.

Good look

pumber ha scritto:
> I've paired up the headset with my notebook, I believe.(please see the
> picture)
>
> However, how can I ouput the sound to the BT headset ??
> Thank you !
>
> ** Attachment added: "Itech_S38.jpg"
> http://launchpadlibrarian.net/21223927/Itech_S38.jpg
>
>

When do we see a permanent fix for this bug?

Ciao,

Sorry but i am a normal linux user, not a developer or programmer.
I wrote my experience to help anybody to bypass the problem until a fix
is released.

Good look and happy 2009

Daniel Lupulescu ha scritto:
> When do we see a permanent fix for this bug?
>
>

Thank you roberto.

My bluetooth headset (for phone usage) needed pin 1234 instead of 0000 :-(.

Can't the developers attempt to connect to the bluetooth device again if automation fails?
Only this time just ask the user for the pin?

smertz,

do as the other did, give the output of the following
1) hcitool scan
2) hcitool inq [bluetooth address]
3) The model of your device

thanks

On Thu, Jan 22, 2009 at 2:29 AM, smerz <email address hidden> wrote:
> Thank you roberto.
>
> My bluetooth headset (for phone usage) needed pin 1234 instead of 0000
> :-(.
>
> Can't the developers attempt to connect to the bluetooth device again if automation fails?
> Only this time just ask the user for the pin?
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a member of
> Bluetooth, which is subscribed to bluez-gnome in ubuntu.
>
> --
> Ubuntu-bluetooth mailing list
> <email address hidden>
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-bluetooth
>

--
Baptiste Mille-Mathias
Les gens heureux ne sont pas pressés

Please check my solution: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502/comments/50

It worked and now I can successfully pair (and talk of course) my bluetooth headset (Plantronics 510).

Cheers,

Igor Gomes

Hello folks,

I did read the solution and got my headset working.
Just a gui type solution would be nice i guess :).

I use intrepid 64bit version and redirecting sound to
my bluetooth headset works, but only static arrives.

Thats not related to this bug however :-)

Cheers

I can confirm that my bluetooth headset (SouthWing SA505) does pair correctly with Jaunty Jackalope 9.04 alpha (1/23/09 daily build). The wizard tried PIN 0000 successfully paired. I don't know if other PINs would work as well, but 0000 will successfully pair.

I did a git clone git://git.kernel.org/pub/scm/bluetooth/bluez.git
of the repository and used bluez/test/simple-agent hci0 00:13:6C:BC:23:6F to connect and typed in 0000 as pin.

hcitool scan
Scanning ...
 00:13:6C:BC:23:6F TomTom Remote

 hcitool inq 00:13:6C:BC:23:6FInquiring ...
 00:13:6C:BC:23:6F clock offset: 0x65d4 class: 0x000540

Hello folks

I followed Igor's procedure, and got a bit further with my ubuntu 8.10 / Lenovo T61p / Plantronics P590 combination.
hcitool scan
Scanning ...
        00:03:89:82:66:26 590Plantronics
hcitool inq
Inquiring ...
        00:03:89:82:66:26 clock offset: 0x4740 class: 0x240404

I could even hear some wav sounds with aplay ... sometimes:

aplay -Dplug:bluetooth /usr/share/sounds/k3b_error1.wav
Playing WAVE '/usr/share/sounds/k3b_error1.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono

==> yes, but one second later

aplay -Dplug:bluetooth /usr/share/sounds/k3b_error1.wav
Playing WAVE '/usr/share/sounds/k3b_error1.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono
aplay: pcm_write:1394: write error: Input/output error

It still doesnt look like i have a fully useable "device" around. Neither kmix nor audio setup or any
other utility seems to be willing to accept my headset.

Any idea what is missing?

On mar, 2009-02-10 at 12:01 +0000, Ed Guenter wrote:

> I could even hear some wav sounds with aplay ... sometimes:
>
> aplay -Dplug:bluetooth /usr/share/sounds/k3b_error1.wav
> Playing WAVE '/usr/share/sounds/k3b_error1.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono
>
> ==> yes, but one second later
>
> aplay -Dplug:bluetooth /usr/share/sounds/k3b_error1.wav
> Playing WAVE '/usr/share/sounds/k3b_error1.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono
> aplay: pcm_write:1394: write error: Input/output error
>
> It still doesnt look like i have a fully useable "device" around. Neither kmix nor audio setup or any
> other utility seems to be willing to accept my headset.
>
> Any idea what is missing?

Ed, please stickn with the subject of the bug, else this is
unmanageable. Such question should go in the forum or in Answers in
Launchpad.

thanks :)

# hcitool scan
Scanning ...
 00:1D:D8:97:42:DE Microsoft Bluetooth Notebook Mouse 5000

# hcitool inq 00:1D:D8:97:42:DE
Inquiring ...
 00:1D:D8:97:42:DE clock offset: 0x79fd class: 0x002580
 00:1E:52:EF:B3:BA clock offset: 0x75dc class: 0x380104

Fixed PIN is "0000"

$hcitool scan
Scanning ...
 00:0D:B5:32:FC:EE BT-GPS-32FCEE

$hcitool inq
 00:0D:B5:32:FC:EE Clock offset: 0x303d class: 0x001f00

Device model: GlobalSat BT-328 Bluetooth GPS Receiver
Fixed PIN: 0000

 hcitool scan --refresh
Scanning ...
 00:0F:F6:30:B8:36 BT-GPS
 00:16:4E:23:1C:92 Jam
$ hcitool inq 00:0F:F6:30:B8:36
Inquiring ...
 00:1D:6E:79:AE:E6 clock offset: 0x01e3 class: 0x5a020c
 00:1F:E3:84:8B:1E clock offset: 0x33f7 class: 0x5a0204
 00:16:4E:23:1C:92 clock offset: 0x0434 class: 0x50020c
 00:0F:F6:30:B8:36 clock offset: 0x56b2 class: 0x500204

GPS fX300

And thanks Roberto, that works great

Hey, look at Gnome bugzilla. Bastien started to fix the things, code is already in the tree:

http://bugzilla.gnome.org/show_bug.cgi?id=560315

Fix was proposed by Vincent Untz (thank you, thank you, thank you !):

http://bugzilla.gnome.org/show_bug.cgi?id=570457

Bastien also has added several new bugs there:

http://bugzilla.gnome.org/browse.cgi?product=gnome-bluetooth

# hcitool scan
Scanning ...
        00:0D:47:01:D5:6D BTH-05
# hcitool inq
Inquiring ...
        00:0D:47:01:D5:6D clock offset: 0x4857 class: 0x200404

device: X-Sport BTH-05 Bluetooth Headset
pin: 1234

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.

$hcitool scan
Scanning ...
 00:1C:88:11:XX:XX PENTA-GPS
$ hcitool inq 00:1C:88:11:XX:XX
Inquiring ...
 00:1C:88:11:XX:XX clock offset: 0x0425 class: 0x001f00

device: Pentagram Pathfinder P3106 GPS BT Receiver
pin: 0000

I am not sure why the status on launchpad is still "unknown" but this bug has been fixed upstream:

http://bugzilla.gnome.org/show_bug.cgi?id=570457

This affects a lot of bluetooth devices, and fix was committed upstream. We ought to fix this in Jaunty.

Upstream bug, (which is linked in the ubuntu bug) has a patch, but was
not commited.
Bastien commited another patch on gnome-bluetooth (which is a fork of
bluez-gnome), but I'm not sure this is can be integrated as it is in
bluez-gnome.

Hi,

This bug also affects my Sagem BT SH1 headset.

hcitool scan :
00:0D:3C:xx:xx:xx Sagem BT SH1

hcitool inq :
00:0D:3C:xx:xx:xx clock offset: 0x36d2 class: 0x240404

The correct pin code is 8888.
Thanks.

Same problem with Navilock BT-359 GPS receiver:

[root@gbalage balage]# hcitool scan
Scanning ...
 00:0D:B5:38:37:26 BT-GPS-383726
[root@gbalage balage]# hcitool inq 00:0d:b5:38:37:26
Inquiring ...
 00:0D:B5:38:37:26 clock offset: 0x051f class: 0x001f00

The correct pin code is 0000

Thx, B;

Hello,

Can people test my bluez-gnome (1.8-0ubuntu3) package from my ppa (https://edge.launchpad.net/~bmillemathias/+archive/ppa), it has a fix for fixed PIN code device.

Tell me if it fixe your problem or not.

Regards.

No. Still the same. Nothing found in Intrepid repo, used Jaunty one. after install i restart bluetooth, no reboot b/c it's live system. Pairing failed. BT dev: Photosmart D5160 printer.

I am also affected, GPS mouse doent work since 8.10. This is apparently fixed upstream for Gnome 2.27.
Does that mean there is no bluetooth GPS device support until Ubuntu 9.10, because Jaunty 9.04 will use Gnome 2.26?!

@Baptiste Mille-Mathias, it worked Perfectly for my GPSlim 236 BUT I had to bump from intrepid to jaunty (you depend on libgtk >=2.15.0 and libdbus-glib >= 0.78)

To keep Google happy, Tags:

Cannot Pair GPS with Ubuntu
ubuntu 8.10 bluetooth gps problems
Holux GPSlim 236 Ubuntu Pairing Key (0000)

@SteveClement, yeah my package was built for jaunty.
@Olaf, no we won't upgrade to the version 2.27 which is an work-in-progres and unstable version.

>Does that mean there is no bluetooth GPS device support until Ubuntu 9.10, because Jaunty 9.04 will use Gnome 2.26?!

Sort of, no devices that wont allow you to enter a pin and that haven't had their pin hard coded will work without using the terminal. If you post the information for your device* then your device might work by default by Jaunty, but yes, there probably wont be a general solution by Jaunty and it's not a great situation without one.

*
1) hcitool scan
2) hcitool inq [bluetooth address]
3) The model of your device
4) The pin code for your device

UI freeze approved, since this is a high importance bug.

This bug was fixed in the package bluez-gnome - 1.8-0ubuntu3

---------------
bluez-gnome (1.8-0ubuntu3) jaunty; urgency=low

  * Add 10_wizard-custom-pin.patch: Allow the user to enter a custom PIN for
    pairing; A lot of devices use a hardcoded PIN and do not have a keyboard
    for entering a random one. Patch by Vincent Untz, merci! (LP: #284994)

 -- Martin Pitt <email address hidden> Mon, 16 Mar 2009 13:26:00 +0100

Hello documentation team,

I just applied Vincent Untz's patch to allow custom PIN numbers in the
bluetooth pairing dialog, please see https://launchpad.net/bugs/284994

I am sorry if that disturbs any screenshots or documentation. Is there
any existing one that needs changing now?

I provided an updated screenshot of the affected dialog:
http://people.ubuntu.com/~pitti/tmp/bluetooth-pin-dialog.png

Thanks,

Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

I couldn't find a link to the specific patch.

Just one check - some pins are 8 characters, I think the specification
maximum is 16 but the dialog box looks like it will only take 4
characters.

(also note 0000 is not the same as 00000000 for BT pins so text size matters).

So the text box should return a variable length string up to 16
characters. I don't have a problem if it scrolls horizontally.

On Mon, Mar 16, 2009 at 8:43 AM, Martin Pitt <email address hidden> wrote:
> Hello documentation team,
>
> I just applied Vincent Untz's patch to allow custom PIN numbers in the
> bluetooth pairing dialog, please see https://launchpad.net/bugs/284994
>
> I am sorry if that disturbs any screenshots or documentation. Is there
> any existing one that needs changing now?
>
> I provided an updated screenshot of the affected dialog:
> http://people.ubuntu.com/~pitti/tmp/bluetooth-pin-dialog.png
>
> Thanks,
>
> Martin
> --
> Martin Pitt                        | http://www.piware.de
> Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

tz: The patch is attached to the upstream bug linked here: http://bugzilla.gnome.org/attachment.cgi?id=127898&action=view

If you think that the pin length is a real issue, please open a separate bug. The fixed length 4 is used in several places in the code, and it's not an obvious and trivial change, so it should be tracked appropriately. Thanks!

thanks a lot for fixing this, I'll be a happy bluetooth GPS mouse user.
Are there any chances to get this fix into an Intrepid update as well? That's still the current version...

I think the only change would be to the maximum length (change 4 to 16
with the ////... line):

+ hbox_custom = gtk_hbox_new(FALSE, 6);
+ radio_custom =
gtk_radio_button_new_with_label_from_widget(GTK_RADIO_BUTTON(radio_0000),
_("Custom PIN code:"));
+ entry_custom = gtk_entry_new_with_max_length(4);
///////////////////////////////////////////////////////////////////////
+ gtk_entry_set_width_chars(GTK_ENTRY(entry_custom), 4);
+ g_signal_connect (entry_custom, "key-press-event",
+ G_CALLBACK (entry_custom_event), NULL);
+ g_signal_connect (entry_custom, "changed",
+ G_CALLBACK (entry_custom_changed), NULL);
+ gtk_box_pack_start(GTK_BOX(hbox_custom), radio_custom,
+ FALSE, FALSE, 0);
+ gtk_box_pack_start(GTK_BOX(hbox_custom), entry_custom,
+ FALSE, FALSE, 0);
+ gtk_container_add(GTK_CONTAINER(vbox_fixed), hbox_custom);

I'll file a separate bug, but this goes to one of the original
problems that short pincodes are insecure and they didn't allow
options for longer ones.

On Mon, Mar 16, 2009 at 12:02 PM, Martin Pitt <email address hidden> wrote:
> tz: The patch is attached to the upstream bug linked here:
> http://bugzilla.gnome.org/attachment.cgi?id=127898&action=view
>
> If you think that the pin length is a real issue, please open a separate
> bug. The fixed length 4 is used in several places in the code, and it's
> not an obvious and trivial change, so it should be tracked
> appropriately. Thanks!
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

My fixed pin device now works in newest Jaunty release. Holux m1200 :)

On Fri, Mar 20, 2009 at 10:39 AM, GBalage <email address hidden> wrote:

> ** Changed in: bluez-gnome (Fedora)
> Status: New => Confirmed
>
> --
> bluetooth-wizard unable to pair to fixed pin devices
> https://bugs.launchpad.net/bugs/284994
> You received this bug notification because you are a direct subscriber
> of the bug.
>

who the hell decided to set a dependency on bluez-gnome on Fedora !!!

Just a big thank you for applying this fix.

Orange Bluetooth Speaker (Acoustic Energy) owner here.

Small glitch, I need guidance here (ubuntu 8.10 32-bit user)

I have read all the posts here and tried to install the package according to the instruction in the installation doc.

when i run the command "./configure" , at the end I get an error message:

"configure: error: D-Bus library is required"

I tried to find the dbus library files from the synaptic, but at the end did not know, which file to install. Can you please tell me the library file name or the command to type to get these installed?

Thank you all

teodor_kasap [2009-04-23 2:26 -0000]:
> "configure: error: D-Bus library is required"

Try installing libdbus-1-dev.

Thank you Martin

I tried it but now get:
"configure: error: GLib library version 2.14 or later is required"

again there are man y glib library packages, which one should i install?

Le jeudi 23 avril 2009 à 02:26 +0000, teodor_kasap a écrit :
> Small glitch, I need guidance here (ubuntu 8.10 32-bit user)
>
> I have read all the posts here and tried to install the package
> according to the instruction in the installation doc.
>
> when i run the command "./configure" , at the end I get an error
> message:
>
> "configure: error: D-Bus library is required"
>
> I tried to find the dbus library files from the synaptic, but at the end
> did not know, which file to install. Can you please tell me the library
> file name or the command to type to get these installed?
>
> Thank you all
>

Teodor,

I don't know what you're trying to achieve, because the fix is already
published in jaunty, but to have all dependency you can type "apt-get
build-dep bluez-gnome, but
1) this bug report is not a support forum, so your question should be
asked elsewhere.
2) Debian/ubuntu have their won building system which is far way better
than manual building.

Regards

Hi Mathias

Thanks for the suggestion.

I am only trying to connect my headset to my computer. I was looking for a fix and found this forum, I'm not exactly an expert on this...

Regards

Le jeudi 23 avril 2009 à 08:51 +0000, teodor_kasap a écrit :
> Hi Mathias
>
> Thanks for the suggestion.
>
> I am only trying to connect my headset to my computer. I was looking for
> a fix and found this forum, I'm not exactly an expert on this...

And as I said, this is not a forum, this is a bug tracker, the forums
are located at http://ubuntuforums.org/
>
> Regards
>

I just got a generic bluetooth mouse off ebay and it works great in XP but I can't connect in Gnome because the bluetooth tool REQUIRES a PIN?! The mouse doesn't have a PIN at all... not 0000, not 1234, not anything. why do you force a pin anyways?! i tried "use fixed pin code" > "custom pin code" but it won't let me leave it blank! ugh.

$ sudo hcitool info 00:11:67:FF:2E:43
Requesting information ...
 BD Address: 00:11:67:FF:2E:43
 Device Name: Bluetooth Mouse
 LMP Version: 2.1 (0x4) LMP Subversion: 0x318
 Manufacturer: Integrated System Solution Corp. (57)
 Features page 0: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
  <3-slot packets>
 Features page 1: 0xff 0xfe 0xff 0x7e 0x98 0x1f 0x19 0x82

I just got a generic bluetooth mouse off ebay and it works great in XP but I can't connect in Gnome because the bluetooth tool REQUIRES a PIN?! The mouse doesn't have a PIN at all... not 0000, not 1234, not anything. why do you force a pin anyways?! i tried "use fixed pin code" > "custom pin code" but it won't let me leave it blank! ugh.

$ sudo hcitool info 00:11:67:FF:2E:43
Requesting information ...
 BD Address: 00:11:67:FF:2E:43
 Device Name: Bluetooth Mouse
 LMP Version: 2.1 (0x4) LMP Subversion: 0x318
 Manufacturer: Integrated System Solution Corp. (57)
 Features page 0: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
  <3-slot packets>
 Features page 1: 0xff 0xfe 0xff 0x7e 0x98 0x1f 0x19 0x82

I'm using Ubuntu 9.04 on a Dell Mini9

@Daevid Vincent

See: http://lists.usefulinc.com/pipermail/gnome-bluetooth/2003-December/000219.html

Looks like this is a different bug to me.

I disagree Robie. The problem relates to the fact that the bluetooth GUI tool requires a PIN. Earlier in this thread, it was about that people couldn't choose a PIN, or use the standard 0000, 1234, 1111, etc. Then that was solved, but now there are devices such as my mouse that require NO PIN at all. The GUI doesn't allow for this case. It FORCES you to choose a PIN. As a user, I should NEVER have to drop to a command line and execute some cryptic commands or muck with "auth encrypt" or whatever that is. The GUI tool just needs to be smarter (or in this case, dumber) and let me enter NO PIN. In fact, it could even be another radio button like so:

( ) 0000
( ) 1111
( ) 1234
( ) custom PIN [_____]
( ) no pin required

Is issue #284994 related?

I'm using a device that has an alphanumeric pin, eg: 9E49. Unfortunately, only numeric input is allowed.

Workaround for needing to add text pin is to install blueman, and pair with that utility:

sudo apt-get install blueman
blueman-manager -> search -> -> right click device -> setup...

In Ubuntu 13.04 and 13.10, trying do pair a GPS data logger device, after select "0000" code, wizard asks me to enter a random code, what is impossible, because it don't have keyboard.
Can somebody help me?

Blueman worked for me. The default gnome GUI still has the bug in Ubuntu 16.10