Pairing: passcode dialogue disappears in <1 second

Bug #241000 reported by Paul Sladen
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Fix Released
Undecided
Unassigned
bluez-utils (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: bluez-utils

The pairing dialogues to allow entering a pin and initiate pairing disappear too fast.

If I do the following:

  sudo hcitool cc 00:19:DB:0A:xx:yy && sudo hcitool auth 00:19:DB:0A:xx:yy

a notifier window will pop up for ~1 second and then disappear.

If I click on the notifier window fastest, the main passcode/pincode entry dialogue will disappear. This also disappears within 1second.

The key seems to be that it is necessary to 'auth', click and 'pincode' within 1 second of a connection being made. This should actually wait until the user is able to and none of the dialogue boxes should cut-off early and disappear without warning.

Forum post discussing the same thing, with screenshots:

  http://ph.ubuntuforums.com/showthread.php?p=5044322

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Which version of ubuntu are you using and which version of bluez-* packages.
I remember seeing this bug back in previous version than hardy, it seems this is fixed now.

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Paul,

could you answer?

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

No answer so far, closing as incomplete

Changed in bluez-utils:
status: New → Incomplete
Revision history for this message
John Pye (jdpipe) wrote :
Download full text (3.6 KiB)

I am also seeing this problem. The connection appears to drop even if I don't attempt the 'hcitool auth' command. Below is the output from 'hcidump -X -V'. I am using Ubuntu Hardy, all up to date and current with standard repositories. My headset is Nokia BH-501.

john@roadwork:~$ dpkg -l bluez*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=========================-=========================-==================================================================
ii bluez-audio 3.26-0ubuntu6 Bluetooth audio support
ii bluez-btsco 1:0.50-0ubuntu2 Bluez Bluetooth SCO tool
ii bluez-cups 3.26-0ubuntu6 Bluetooth printer driver for CUPS
un bluez-firmware <none> (no description available)
ii bluez-gnome 0.25-0ubuntu1 Bluetooth utilities for GNOME
ii bluez-hcidump 1.40-0ubuntu1 Analyses Bluetooth HCI packets
un bluez-pan <none> (no description available)
un bluez-passkey-gnome <none> (no description available)
un bluez-sdp <none> (no description available)
ii bluez-utils 3.26-0ubuntu6 Bluetooth tools and daemons

HCI sniffer - Bluetooth packet analyzer ver 1.40
device: hci0 snap_len: 1028 filter: 0xffffffff

< HCI Command: Create Connection (0x01|0x0005) plen 13
    bdaddr 00:0D:3C:A6:E8:1C ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
    Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
    Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
    status 0x00 handle 11 bdaddr 00:0D:3C:A6:E8:1C type ACL encrypt 0x00
< ACL data: handle 11 flags 0x02 dlen 10
    L2CAP(s): Info req: type 2
< HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2
    handle 11
> HCI Event: Read Remote Supported Features (0x0b) plen 11
    status 0x00 handle 11
    Features: 0xff 0xff 0x8f 0x78 0x18 0x18 0x00 0x80
> HCI Event: Command Status (0x0f) plen 4
    Read Remote Supported Features (0x01|0x001b) status 0x00 ncmd 1
< HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
    handle 11 policy 0x0f
    Link policy: RSWITCH HOLD SNIFF PARK
> HCI Event: Command Complete (0x0e) plen 6
    Write Link Policy Settings (0x02|0x000d) ncmd 1
    status 0x00 handle 11
< HCI Command: Remote Name Request (0x01|0x0019) plen 10
    bdaddr 00:0D:3C:A6:E8:1C mode 2 clkoffset 0x0000
> HCI Event: Command Status (0x0f) plen 4
    Remote Name Request (0x01|0x0019) status 0x00 ncmd 1
> HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
    bdaddr 00:0D:3C:A6:E8:1C mode 1
> HCI Event: Max Slots Change (0x1b) plen 3
    handle 11 slots 5
> ACL data: handle 11 flags 0x02 dlen 16
    L2CAP(s): Info rsp: type 2 result 0
      Extended feature mask 0x0000
> HCI Event: Remote Name Req Complete (0x07) ple...

Read more...

Revision history for this message
John Pye (jdpipe) wrote :

Reopened with new info

Changed in bluez-utils:
status: Incomplete → New
Revision history for this message
John Pye (jdpipe) wrote :

I should add that the Nokia BH-501 headset apparently supports Bluetooth 1.2 but not Bluetooth 2.0, and also that when pairing the headset with my Nokia phone, there appears not to be any such timeout issue; the pairing works fine.

Cheers
JP

Revision history for this message
John Pye (jdpipe) wrote :

Whatever the problem is with bluez-gnome, it seems that Blueman is able to resolve the problem, by allowing a 'connect to audio device --> headset' option, which worked for me. Not sure what it means, but I did manage to resolve my pairing problem:
http://ubuntuforums.org/showthread.php?p=5780509#post5780509

Cheers
JP

Revision history for this message
Bruno L. Juchli (bruno-juchli) wrote :

Hi everybody,

same problem here:
Ubuntu 8.04 with all the updates
bluez-audio, -cups, -utils 3.26-0ubuntu6
bluez-gnome 0.25-0ubuntu1

trying to pair with a Dell D630 with Dell 360 Bluetooth chipset (Toshiba Stack).

John Pye (jdpipe)
Changed in bluez-utils:
status: New → Confirmed
Revision history for this message
Mario Limonciello (superm1) wrote :

Can someone retest this on Intrepid? The functionality should be better now.

Changed in bluez-utils:
status: Confirmed → Incomplete
Revision history for this message
Adilson Oliveira (agoliveira) wrote :

I just received a new GPS device Holux 1000B that works perfectly with my Nokia 810 but I can't authenticate on my 8.10 notebook. Looks like this is the same problem.

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote : Re: [Bug 241000] Re: Pairing: passcode dialogue disappears in <1 second

On Thu, Oct 30, 2008 at 7:33 PM, Adilson Oliveira <email address hidden> wrote:
> I just received a new GPS device Holux 1000B that works perfectly with
> my Nokia 810 but I can't authenticate on my 8.10 notebook. Looks like
> this is the same problem.
>
Adilson,

Are you sure this is the same problem? you see the notification
popping-up and disappear immediately after ?

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

Revision history for this message
Damien Laureaux (timoa) wrote :

Same problem with Intrepid 8.10...

dpkg -l bluez*
Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder
| État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements
|/ Err?=(aucune)/H=à garder/besoin Réinstallation/X=les deux (État,Err: majuscule=mauvais)
||/ Nom Version Description
+++-==============-==============-===============================
ii bluez 4.12-0ubuntu5 Bluetooth tools and daemons
ii bluez-alsa 4.12-0ubuntu5 Bluetooth audio support
un bluez-audio <néant> (aucune description n'est disponible)
ii bluez-btsco 1:0.50-0ubuntu Bluez Bluetooth SCO tool
ii bluez-compat 4.12-0ubuntu5 BlueZ 3.x compatibility binaries
ii bluez-cups 4.12-0ubuntu5 Bluetooth printer driver for CUPS
ii bluez-gnome 1.8-0ubuntu1 Bluetooth utilities for GNOME
ii bluez-gstreame 4.12-0ubuntu5 Bluetooth gstreamer support
ii bluez-hcidump 1.42-1build1 Analyses Bluetooth HCI packets
un bluez-input <néant> (aucune description n'est disponible)
un bluez-network <néant> (aucune description n'est disponible)
un bluez-passkey- <néant> (aucune description n'est disponible)
un bluez-serial <néant> (aucune description n'est disponible)
ii bluez-utils 4.12-0ubuntu5 Transitional package

I wan't to pair my Bluetooth GPS (PIN:0000) and my headset (Samsung WEP200) and it not work because popup is to fast to close...

I don't test with Blueman because no package was ready for Intrepid and compiled of source don't work for me (i have no time now to check why...)

Revision history for this message
John Pye (jdpipe) wrote :

This was fixed for me in Intrepid. I notice that the pairing process seems to have changed quite a bit. My old pairing from Hardy needed to be deleted and re-paired, then the headphone worked as it should. Tested with both rhythmbox (using .a2dp/toggle.sh), and Skype.

Changed in bluez:
status: Incomplete → New
Revision history for this message
Richard Mitchell (mitchellrj) wrote :

Same here trying to pair with a Jensen WBT210. Hardy too, same packages.

Revision history for this message
Murz (murznn) wrote :

Confirm the problem on Ubuntu Intrepid i386 with latest updates only
and with additional bluez, compiled from sources:
    * bluez-4.26.tar.gz
    * bluez-gnome-1.8.tar.gz

  sudo hcitool cc 00:19:DB:0A:xx:yy && sudo hcitool auth 00:19:DB:0A:xx:yy

a notifier window will pop up for ~1 second and then disappear.

If I click on the notifier window fastest, the main passcode/pincode entry dialogue will disappear. This also disappears within 1second.

Changed in bluez-utils:
status: New → Confirmed
Revision history for this message
Murz (murznn) wrote :

setting the command
sudo hciconfig hci0 auth
before connecting helps me to prevent disappearing the pin dialog.
I have find this method here:
https://bugs.launchpad.net/fedora/+source/bluez-gnome/+bug/284994/comments/90

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.

Revision history for this message
Baptiste Mille-Mathias (bmillemathias) wrote :

Could you try with jaunty development version or a Jaunty Live CD, I expect that to be fixed.

Revision history for this message
Murz (murznn) wrote :

I have updated my Kubuntu Intrepid to Jaunty beta1 (config-files of bluetooth reset to default), try to pair device. Mobile phone sees my computer, I try to pair, sets the password, but I can't see the pair dialog on KDE and see the error pairing process on mobile phone.

P.S. Bluez have been updated to bluez-4.34 which includes:
This release add more advanced features to the audio support for Handsfree/Headset profiles and also A2DP. Advanced system like PulseAudio should now be able to better interact with BlueZ and also have more control over multi-profile devices.

But Jaunty have a 4.32-0ubuntu4 version. Will be good to see 4.34 in Jaunty!

Revision history for this message
Mario Limonciello (superm1) wrote :

As indicated by one of the posters, this was fixed in Intrepid (with the bluez4.x stuff). Closing the bug.

Changed in bluez-utils (Ubuntu):
status: Confirmed → Invalid
Changed in bluez (Ubuntu):
status: New → Fix Released
Revision history for this message
PaulSchulz (paulschulz) wrote :

I am seeing this bug in Ubuntu 23.10.
bluez 5.68-0ubuntu1.1

Hardware: Logi POP Keys
https://www.logitech.com/en-au/products/keyboards/pop-keys-wireless-mechanical.920-011226.html

I have managed to have it working in the past, but the 6-digit code pop-up disappears very quickly (as described, <1sec).

Revision history for this message
PaulSchulz (paulschulz) wrote :

- This occurs on my daily use laptopm which has been upgraded from 23.04 -> 23.10

- I have just tried to pair on another laptop with freshly installed 23.10
  - The dialog displaying the pairing code persists
    and I can pair correctly with same keyboard (it can pair with 3 separate devices)
  - bluez 5.68-0ubuntu1.1

Revision history for this message
PaulSchulz (paulschulz) wrote :

Resetting the bluez package did NOT fix the problem.
  Removing the bluez package(s), removing /var/lib/bluetooth and re-installing.

  sudo apt remove --purge bluez
  rm -rf /var/lib/bluetooth
  sudo apt install bluez gnome-bluetooth gnome-bluetooth-sendto

The bluetooth system need to be started, and this empties the list of discovered bluetoothe devices,
but the popup for the keyboard auth number disappears again.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This bug has been closed for over 14 years so if you have any current issues then please open new bugs for each of them.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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