I cannot agssociate with other devices that need a pin. I have bluez-pin, pinentry-gtk2 and dbus installed, but this is all I see: Aug 9 21:15:14 lapse hcid[12525]: pin_code_request (sba=00:0F:B3:9A:02:A0, dba=00:07:A4:01:AB:A3) Aug 9 21:15:14 lapse hcid[12525]: Calling PasskeyAgent.Request: name=:1.1, path=/org/bluez/passkey_agent_12536 Nothing else happens, and the docs don't tell me what to do.
I have exactly the same problem. I see this in /var/log/syslog : Aug 10 12:52:57 portatil2 hcid[6332]: pin_code_request (sba=00:80:5A:40:DA:D9, dba=00:18:A4:17:6D:84) Aug 10 12:52:57 portatil2 hcid[6332]: Calling PasskeyAgent.Request: name=:1.3, path=/org/bluez/passkey_agent_6362 Aug 10 12:52:57 portatil2 pppd[13064]: Failed to open /dev/bluetooth/rfcomm/0: Connection refused Aug 10 12:52:57 portatil2 pppd[13064]: Exit. The mobile device I'm trying to connect to do ask for a pin, I enter the pin and it tells the pin is incorrect. Nothing else happens in the computer, and the connection is not established. Regards, Dionisio Martínez Soler dmsoler at mundo-r dot com
Same bug, and i have tested with bluez-utils/3.1-2 and it work fine. how to enable debug information to help you ?
/etc/bluetooth/passkeys/00:07:A4:01:AB:A3 and /etc/init.d/bluetoot restart ? /usr/lib/bluetooth/add-passkey 00:07:A4:01:AB:A3 should show in the processes list filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: I worked myself up from nothing to a state of extreme poverty. -- Groucho Marx
also sprach Filippo Giunchedi <filippo@debian.org> [2006.08.13.1222 +0100]: It does, but I still cannot authenticate with the remote device. If I downgrade to testing, then associate, then upgrade to unstable, then it works to connect. I just cannot reassociate.
the PIN, and ps ax | grep passkey give me: 11745 pts/2 S 0:00 /usr/lib/bluetooth/add-passkey 00:18:A4:17:6D:84 If I try: hcitool cc 00:18:A4:17:6D:84 hcitool auth 00:18:A4:17:6D:84 and I enter the PIN when asked in the mobile device, I get: HCI authentication request failed: Input/output error and the mobile device keeps lots of time in a "Verifying PIN" message. In /var/log/syslog : Aug 13 15:14:27 portatil2 hcid[11724]: link_key_request (sba=00:80:5A:40:DA:D9, dba=00:18:A4:17:6D:84) Aug 13 15:14:27 portatil2 hcid[11724]: pin_code_request (sba=00:80:5A:40:DA:D9, dba=00:18:A4:17:6D:84) Aug 13 15:14:27 portatil2 hcid[11724]: Calling PasskeyAgent.Request: name=:1.10, path=/org/bluez/passkey_agent_11745 And hcidump shows this during the process: HCI sniffer - Bluetooth packet analyzer ver 1.31 device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Create Connection (0x01|0x0005) plen 13 < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4 < HCI Command: Remote Name Request (0x01|0x0019) plen 10 < HCI Command: Authentication Requested (0x01|0x0011) plen 2 < HCI Command: Link Key Request Negative Reply (0x01|0x000c) plen 6 < HCI Command: PIN Code Request Reply (0x01|0x000d) plen 23 Regards, Dionisio Martínez Soler dmsoler at mundo-r dot com
Hi! I think I have the same problem. Here is my syslog: Aug 16 09:54:00 tash hcid[10694]: Bluetooth HCI daemon Aug 16 09:54:00 tash sdpd[10696]: Bluetooth SDP daemon Aug 16 09:54:00 tash hcid[10694]: Register path:/org/bluez fallback:1 Aug 16 09:54:00 tash hcid[10694]: Device hci0 has been added Aug 16 09:54:00 tash hcid[10694]: Starting security manager 0 Aug 16 09:54:00 tash hidd[10698]: Bluetooth HID daemon Aug 16 09:54:00 tash hcid[10694]: Can't write inquiry mode for hci0: Input/output error (5) Aug 16 09:54:00 tash hcid[10694]: Register path:/org/bluez/hci0 fallback:0 Aug 16 09:54:34 tash hcid[10694]: link_key_request (sba=00:03:7A:0A:D9:D9, dba=00:07:E0:8A:62:4E) Aug 16 09:54:34 tash hcid[10694]: pin_code_request (sba=00:03:7A:0A:D9:D9, dba=00:07:E0:8A:62:4E) Aug 16 09:54:34 tash hcid[10694]: call_passkey_agent(): no agent registered It seems that the passkey handler is not registered correctly... Cheers, /rp
Hi again. In my case, I solved the problem by doing echo -n "1234" > /etc/bluetooth/passkeys/00:18:A4:17:6D:84 instead of echo "1234" > /etc/bluetooth/passkeys/00:18:A4:17:6D:84 Apparently, I could not authenticate because of the EOL in the files in /etc/bluetooth/passkeys , as it is suggested in Bug#383188 . Please, try it: perhaps this is also the problem other people in this bug report are seeing Regards, Dionisio Martínez Soler dmsoler at mundo-r dot com
Hi it doesn't work to me...
Aug 17 06:37:52 localhost hcid[23396]: HCI dev 0 registered
Aug 17 06:37:52 localhost hcid[23396]: Device hci0 has been added
Aug 17 06:37:52 localhost hcid[23396]: Register path:/org/bluez/hci0 fallback:0
Aug 17 06:37:52 localhost hcid[23396]: HCI dev 0 up
Aug 17 06:37:52 localhost hcid[23396]: Starting security manager 0
Aug 17 06:37:52 localhost hcid[23396]: Can't write inquiry mode for
hci0: Input/output error (5)
Aug 17 06:39:19 localhost hcid[23396]: link_key_request
(sba=00:20:E0:77:BD:37, dba=00:15:DE:23:EC:87)
Aug 17 06:39:19 localhost hcid[23396]: pin_code_request
(sba=00:20:E0:77:BD:37, dba=00:15:DE:23:EC:87)
Aug 17 06:39:19 localhost hcid[23396]: Calling PasskeyAgent.Request:
name=:1.6, path=/org/bluez/passkey_agent_23404
flambe:/etc/bluetooth/passkeys# echo -n "1234" > 00:15:DE:23:EC:87
flambe:/etc/bluetooth/passkeys# hcitool cc --role=s 00:15:DE:23:EC:87
flambe:/etc/bluetooth/passkeys# hcitool con
Connections:
< ACL 00:15:DE:23:EC:87 handle 41 state 1 lm MASTER
flambe:/etc/bluetooth/passkeys# hcitool auth 00:15:DE:23:EC:87
HCI authentication request failed: Input/output error
My passkey files have only 4 characters as shown in the directory, no end of line, and I still cannot authenticate. My phone (Nokia 6310i) asks me for the PIN and then says "Bluetooth connection aborted". Linux side gets a connection refused on /dev/rfcomm0. Greetings Marc
My passkey files have only 4 characters as shown in the directory, no end of line, and I still cannot authenticate. My phone (Nokia 6310i) asks me for the PIN and then says "Bluetooth connection aborted". Linux side gets a connection refused on /dev/rfcomm0. Greetings Marc
I tried this, it didn't work. I needed to do bluetooth stop, bluetooth start for the passkey to register correctly. Greetings Marc
I tried this, it didn't work. I needed to do bluetooth stop, bluetooth start for the passkey to register correctly. Greetings Marc
this should be fixed (the restart issue) in 3.1-4, do you mind trying again? filippo
this should be fixed (the restart issue) in 3.1-4, do you mind trying again? filippo
What do you want me to do? kill /etc/bluetooth/passkeys, restart bluetooth, see connections fail, re-establish the directory, restart bluetooth again and see whether connections work again? Greetings Marc
What do you want me to do? kill /etc/bluetooth/passkeys, restart bluetooth, see connections fail, re-establish the directory, restart bluetooth again and see whether connections work again? Greetings Marc
try /etc/init.d/bluetooth stop then start, then restart it should work as expected (i.e. add-passkey re-launched after the restart) filippo
Hi, I just ran into the very same problem. Even if I put a PIN without the newline character in /etc/bluetooth/passkeys, the connection fails. The mobiles asks me whether to accept the connection and asks for the PIN as expected, but the connection fails before I am able to enter all four digits. This bug seems to not have been touched for two months. Is anyone still working on fixing it? regards Hadmut
Hi, bluez-utils 3.7-1 has just migrated to testing today, so it should hit your nearest mirror tomorrow, please upgrade to 3.7-1 and don't forget to read /usr/share/doc/bluez-utils/README.Debian for instructions, the /etc/bluetooth/passkeys thing is gone. thanks, filippo
Filippo Giunchedi <filippo@esaurito.net> writes: I don't agree that this problem has been fixed at all. You have simply removed the ability of non-GNOME clients (maybe there's a KDE dbus client as well) to enter a passkey. I don't use GNOME. I don't use KDE. I don't recall this ever having been a problem with any non-GNOME or KDE Debian software before. It's not as if I can even quickly write my own passkey handler in Python or something since dbus seems to be in transition right now and lots and lots will break on my machine (including my power management; powersaved is incompatible with the python version of dbus). Neither can I find the format of the pincodes file because it is not created until a pin is actually entered. Nor could I find it from a cursory glance at the code. I do not believe that a console based method of entering a pin should have been removed from Debian.
On Sun, Nov 12, 2006 at 09:46:43PM +0000, Nic James Ferrier wrote: ... I fully agree with you. The bluez package is currently destructed by intention. BTW, the gnome version wasn't working either on my machine. regards Hadmut
works much, much better than to be destructive and indeed it is much harder as well. filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: Caelum, non animo mutant, qui trans mare currunt Who crosses the sea changes the sky, not the soul. -- Oratius
did you tested bluez-passkey-gnome (or bluez-gnome when it hits the archive) with other DEs and/or WMs? please provide examples of non-functionality please provide specific examples, I see dbus 0.94-1 in testing and -2 in unstable, is it going a transition? how does it breaks packages? I agree that the pincodes format is not documented in README.Debian, and that of course needs to be fixed. FWIW the format is generic for all the bluez storage and it is "key value" so in pincodes it should be "<remoteaddress> <pincode>" (beware of leading and trailing spaces if you are hand-editing the file, though. welcome as always) filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: It's not that I'm afraid to die, I just don't want to be there when it happens. -- Woody Allen
Filippo Giunchedi <filippo@esaurito.net> writes: know, isn't a window manager. I imagine if I was using GNOME with any Window Manager I could still use the GNOME bt-applet. But I don't use GNOME so the applet can't possibly run. I can run it... but it has nowhere to live. Of course... you could say: well run the panel. But running the gnome-panel *is* running gnome and I don't want to run gnome. Ok. Installation of python-dbus would cause these to be removed: openoffice.org* openoffice.org-help-en-us* openoffice.org-writer* python-uno* python2.3-libxml2* python2.3-dbus depends on dbus-1 right now and that causes these to be removed: bluetooth* bluez-passkey-gnome* bluez-utils* dbus* hal* powersaved* Not good. I did work it out. I was very cross about it though. If I have time when the dbus situation is fixed I will write a python tool to respond to dbus querys with a fixed pin. That's really all that's needed.
I haven't tested it, but even if you don't see the applet running it will popup the pin dialog nevertheless. This needs to be tested though. I assumed you are running testing, is that right? Note that python2.3-dbus is not present in testing because of the python transition. great, that'll be much appreciated. filippo
Filippo Giunchedi <filippo@esaurito.net> writes: No. It doesn't do that. stable + testing + unstable with testing being default.
recommends bluez-gnome which is a PIN helper -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: Date: Tuesday, 2002/10/22 - 08:09 dselect proves the existence of Satan. It's the worst part of Debian.
I ran into the same problem: cannot (re)establish a pairing because there is no working pin agent, and trying to install bluez-pin wants to remove bluez-utils. I tried bluetooth-applet, but it did not come up with a pin request at the right time (according to the syslog it did register as bluetooth pin agent). I use fvwm as window manager. I tried multiple ways of entering the pin in the filesystem, none of which worked. Looking at /etc/bluetooth/passkeys/* shows none of those were read by the bluez-utils processes. In the end, I found https://launchpad.net/ubuntu/+source/bluez-utils/+bug/56651 where 'Dan V' shows a workaround to getting at least the passkey-agent compiled. I got far enough to have a compiled passkey-agent, and that worked for the one pairing I needed. Yes, this is quite frustrating, when the basic utilities (bluez-utils) cannot be installed at the same time as a basic pincode agent (bluez-pin). I hope the above url helps people who need a quick fix.
Yes, this bug is reproducible, even with bluez-gnome installed and dbus running. Right now I get: Mar 14 16:56:13 lapse hcid[30166]: Register path:/org/bluez fallback:1 Mar 14 16:56:13 lapse hcid[30166]: Register path:/org/bluez/hci0 fallback:0 [...] Mar 14 16:56:47 lapse hcid[30166]: pin_code_request (sba=00:0F:B3:9A:02:A0, dba=00:18:13:1B:D4:0F) Mar 14 16:56:47 lapse hcid[30166]: call_passkey_agent(): no agent registered If I then restart dbus and try again: Mar 14 16:58:24 lapse hcid[30166]: Got disconnected from the system message bus Mar 14 16:58:29 lapse hcid[30166]: Register path:/org/bluez fallback:1 the request just times out: lapse:~# hidd --connect 00:18:13:1B:D4:0F Can't create HID control channel: Connection refused Also see the bug about segfaults in hcid on amd64, which I just filed.
the segfault on amd64 is gone and now bluez is sensibly better regarding agent, you can use bluez-gnome, gnome-bluetooth or the commandline bluetooth-agent. IMO this bug can be closed, what do you think? filippo -- Filippo Giunchedi - http://esaurito.net - 0x6B79D401 Adapting old programs to fit new machines usually means adapting new machines to behave like old ones. -- Alan Perlis
Laba diena, Noriu Jus informuoti apie šių metų pasikeitimą dėl atnaujintos visos Lietuvos įmonių bazės 2018 metų sausio vidurio. Visi juridiniai asmenys pateikti bazėje yra veikiantys, realiai vykdantys veiklą, turintys įdarbintų darbuotojų. Duomenys pagal Sodrą, Registrų centrą. Bazėje nurodoma ir apyvarta, darbuotojų atlyginimai, darbuotojų skaičius, transporto skaičius ir daug kitų duomenų, kuriuos matysite pavyzdyje. Duomenis galima filtruoti pagal veiklas, miestus ir kitus duomenis. Šią bazę verta turėti visoms įmonėms. Pateiksiu priežastis: 1) Kontaktai pateikti bazėje direktorių ir kitų atsakingų asmenų, didelė tikimybė Jums surasti naujų klientų, partnerių, tiekėjų, kai tiesiogiai bendrausite su direktoriais, komercijos vadovais. 2) Konkurentų analizavimas, tiekėjų atsirinkimas pagal Jums reikalingus kriterijus, galite atsifiltruoti pagal įmonės dydį, bazėje nurodoma kiek įmonės skolingos Sodrai. 3) Lengva, greita ir patogu dirbti su šia baze, elektroninius pašto adresus galite importuoti į elektroninių laiškų siuntimo programas ar sistemas iš kurių siunčiate elektroninius laiškus. Taip pat galite importuoti mobiliųjų telefonų numerius į SMS siuntimo programas. Išsirinkite iš "Veiklų sąrašo" veiklas kurių Jums reikia. ( Sąrašas prisegtas laiške excel faile ) Parašykite, kurias veiklas išsirinkote ir atsiųsime pavyzdį ir pasiūlymą su sąlygomis įmonių bazei įsigyti Pagarbiai, Tadas Giedraitis Tel. nr. +37067881041
Laba diena, Noriu Jus informuoti apie šių metų pasikeitimą dėl atnaujintos visos Lietuvos įmonių bazės 2018 metų sausio vidurio. Visi juridiniai asmenys pateikti bazėje yra veikiantys, realiai vykdantys veiklą, turintys įdarbintų darbuotojų. Duomenys pagal Sodrą, Registrų centrą. Bazėje nurodoma ir apyvarta, darbuotojų atlyginimai, darbuotojų skaičius, transporto skaičius ir daug kitų duomenų, kuriuos matysite pavyzdyje. Duomenis galima filtruoti pagal veiklas, miestus ir kitus duomenis. Šią bazę verta turėti visoms įmonėms. Pateiksiu priežastis: 1) Kontaktai pateikti bazėje direktorių ir kitų atsakingų asmenų, didelė tikimybė Jums surasti naujų klientų, partnerių, tiekėjų, kai tiesiogiai bendrausite su direktoriais, komercijos vadovais. 2) Konkurentų analizavimas, tiekėjų atsirinkimas pagal Jums reikalingus kriterijus, galite atsifiltruoti pagal įmonės dydį, bazėje nurodoma kiek įmonės skolingos Sodrai. 3) Lengva, greita ir patogu dirbti su šia baze, elektroninius pašto adresus galite importuoti į elektroninių laiškų siuntimo programas ar sistemas iš kurių siunčiate elektroninius laiškus. Taip pat galite importuoti mobiliųjų telefonų numerius į SMS siuntimo programas. Išsirinkite iš "Veiklų sąrašo" veiklas kurių Jums reikia. ( Sąrašas prisegtas laiške excel faile ) Parašykite, kurias veiklas išsirinkote ir atsiųsime pavyzdį ir pasiūlymą su sąlygomis įmonių bazei įsigyti Pagarbiai, Tadas Giedraitis Tel. nr. +37067881041
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation? I cannot use my bluetooth (ATHEROS AR3011) because it does not load in firmware. Works fine in Ubuntu. Seems it's a bug from 2011.
* What exactly did you do (or not do) that was effective (or
ineffective)? Nothing was effective, only changing distro.
* What was the outcome of this action? Works fine in Ubuntu 20.04 and 22.04.
* What outcome did you expect instead? That my bluetooth works normal.
*** End of the template - remove these template lines ***