#463711 cannot pair on the command line

Package:
src:bluez
Source:
bluez
Submitter:
Harald Dunkel
Date:
2021-01-31 06:33:04 UTC
Severity:
normal
#463711#5
Date:
2008-02-02 15:52:30 UTC
From:
To:
If I try to connect my bluetooth headset with hcitool, then
I get

# hcitool scan
Scanning ...
         00:0A:94:A1:4A:42       BTST-9300
# hcitool cc 00:0A:94:A1:4A:42 && echo success
success
# hcitool con
Connections:


Thats all. No connections are listed. AFAIU it should have
listed 00:0A:94:A1:4A:42. Of course the headset was set to
pairing mode.

Please note that neither gnome-bluez nor kdebluetooth work
for me. But since it doesn't work on the command line
either I doubt that this is a failure of the GUI framework.


Regards

Harri
#463711#10
Date:
2008-02-16 17:45:19 UTC
From:
To:
Hello,
bluez-gnome or kdebluetooth) will pop up a dialog asking the passkey.

To send some audio to your headset follow
http://wiki.bluez.org/wiki/HOWTO/AudioDevices

thanks,
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:

If there is any better use for being famous and respected than using
that status to question orthodoxy, I haven't found it yet.
-- Eric S. Raymond
#463711#15
Date:
2008-02-17 08:25:47 UTC
From:
To:
Filippo Giunchedi wrote:
kdebluetooth work for me." The bug report is about using bluez
on the command line. Currently it says "success", but obviously
it failed, not giving any hint about what went wrong. That's the
bug.


Regards

Harri
#463711#20
Date:
2008-02-17 09:52:10 UTC
From:
To:
requests as:

Feb 16 18:38:35 clamp hcid[24523]: pin_code_request (sba=XXXXXXXXXXX, dba=XXXXXXXXXX)

Currently there is no console passkey agent (besides the example in
/usr/share/doc/bluez-utils/examples/ )

HTH,
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:

"I drank what?"
-- Socrates
#463711#25
Date:
2008-10-18 14:22:23 UTC
From:
To:
Same here!

IMHO this is exactly the same bug as #416484.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416484

The KDE framework doesn't ask me for a pin but it also doesn't work from
the command line as described here.

This issue is happening to me since at least a year, it was working fine
before!! And yes, i checked tons of different settings, googled for it,
spent hours on it and cannot find anything wrong in my setup. It simply
doesn't work :-(
Devices which were paired earlier continue to work fine!! it is just new
devices which i want to add which make problems!

No messages at all in any logs, in particular nothing logged
in /var/log/daemon.log  after hcid started.
#463711#30
Date:
2008-10-18 14:31:03 UTC
From:
To:
There is also
http://bugs.pardus.org.tr/show_bug.cgi?id=7500
which is exactly the same problem... :-(

I wonder why it doesn't work in just some cases... :-(
#463711#35
Date:
2009-06-19 20:45:44 UTC
From:
To:
this should be now fixed with bluez 4, can you please retry?

filippo
--
Filippo Giunchedi - http://esaurito.net - 0x6B79D401

Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by
definition, not smart enough to debug it.
-- Brian W. Kernighan
#463711#40
Date:
2009-06-21 05:13:29 UTC
From:
To:
Filippo Giunchedi wrote:
"hcitool con" there was still no message about anything
requesting a pin:

Jun 21 07:05:03 daffy dbus-daemon: Reloaded configuration
Jun 21 07:05:04 daffy last message repeated 2 times
Jun 21 07:05:05 daffy bluetoothd[12717]: Bluetooth daemon 4.40
Jun 21 07:05:05 daffy bluetoothd[12717]: Starting SDP server
Jun 21 07:05:05 daffy bluetoothd[12717]: bridge pan0 created
Jun 21 07:05:05 daffy bluetoothd[12717]: Starting experimental netlink support
Jun 21 07:05:05 daffy bluetoothd[12717]: Failed to find Bluetooth netlink family
Jun 21 07:05:05 daffy bluetoothd[12717]: HCI dev 0 registered
Jun 21 07:05:05 daffy bluetoothd[12717]: HCI dev 0 up
Jun 21 07:05:05 daffy bluetoothd[12717]: Starting security manager 0
Jun 21 07:05:05 daffy bluetoothd[12717]: Adapter /org/bluez/12717/hci0 has been enabled


Regards

Harri
#463711#45
Date:
2009-06-21 08:25:20 UTC
From:
To:
with cc you should see something like

Jun 21 09:33:08 clamp bluetoothd[3104]: pin_code_request (sba=00:1E:52:DA:5E:C1, dba=00:03:89:99:04:98)

or if the headset is already paired

Jun 21 09:33:08 clamp bluetoothd[3104]: link_key_request (sba=00:1E:52:DA:5E:C1, dba=00:03:89:99:04:98)

filippo
--
Filippo Giunchedi - http://esaurito.net - 0x6B79D401

UNIX was not designed to stop its users from doing stupid things, as that
would also stop them from doing clever things.
-- Doug Gwyn
#463711#50
Date:
2009-06-21 10:15:04 UTC
From:
To:
"hcitool cc <bdaddr>" gave me the promised link_key_request message
in /var/log/daemon.log. On stderr I got

	Can't create connection: Input/output error

There was no message about a pin_code_request, AFAICS. Maybe
the ultra-secret pin of the headset ("0000") is hardwired somewhere.
I made sure that /var/lib/bluetooth/<bdaddr>/pincodes doesn't exist,
but if it is there it doesn't make a difference.

There was no sound. Trying to play a *.mp3 file mplayer showed me

[AO_ALSA] alsa-lib: pcm_bluetooth.c:1607:(audioservice_expect) BT_GET_CAPABILITIES failed : Input/output error(5)
[AO_ALSA] Playback open error: Input/output error
Failed to initialize audio driver 'alsa'
Could not open/initialize audio device -> no sound.

I verified the headset using my PDA and Audiogateway.


Regards

Harri