Summary: | kbluetoothd - authentication error | ||
---|---|---|---|
Product: | kde-bluetooth | Reporter: | Ruben Jenster <rjenster> |
Component: | kbluetoothd | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
kbluetooth popup
hcid.conf |
Description
Ruben Jenster
2005-05-01 02:16:32 UTC
Created attachment 10865 [details]
kbluetooth popup
Created attachment 10866 [details]
hcid.conf
It's probably not a problem with kdebluetooth. If if initiate the pairing process with your headset, then BlueZ will handle most of the work on the PC side. kdebluetooth is only used to show the pin helper. And since the pin dialog is working when the devices are not paired, there should be no problem with the pin helper setup. Maybe the link key manager of kdebluetooth has messed up the link key file of kdebluetooth when you removed the pairing. Try to delete the link_key file in /etc/bluetooth manually, restart hcid, pair your headset and then try to pair a second time - does it work then? hcid.conf looks good in my eyes. thanks a lot - that was exactly the problem :-) Hm, that's not really a solution. It would be great if you could try to reproduce the error. Maybe the kdebluetooth link key manager caused the problem, maybe something else. We should find out what it was. Well it's seems to be more complicated my problem. I tried my USB bluetooth dongle on my laptop -> same behaviour there. I always have to delete the link_key before pairing my headset again. The curious thing is, that when I use the build in bluetooth module of my thinkpad the pin-helper always asks for the pin even if the headset has allready been paired. I will ask the bluez people - maybe they can help me. |