From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] link_key pairing problem
Date: Mon, 23 May 2005 12:08:33 +0200 [thread overview]
Message-ID: <1116842913.30044.36.camel@pegasus> (raw)
In-Reply-To: <200505211500.37962.ruben@hotheads.de>
Hi Ruben,
> I hoped to get rid of the pairing problem with my headset but it still exists.
> I had to manually delete the link_key file in /etc/bluetooth. I found a ugly
> and simple hack: Symlinked /dev/null to /etc/bluetooth/link_key so that
> everything that gets written to link_key is automatically deleted. This way
> repairing works but it's not a clean way. I think there is a problem with the
> pairing mechanism in bluez. Or could that be a problem of my headset/dongle?
>
> Actually I'm using bluez-utils /bluez-libs version 2.15. I allready tried 2.16
> but that doesn't solve the problem.
use bluez-utils-2.17 and use a clean start. Don't modify hcid.conf and
remove the link_key file (new place and file format since 2.16). Run
"hcidump -X -V" to show what happens.
Maybe your headset is broken.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-23 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 13:00 [Bluez-devel] link_key pairing problem Ruben Jenster
2005-05-23 10:08 ` Marcel Holtmann [this message]
2005-05-25 12:47 ` Ruben Jenster
2005-05-25 13:26 ` Marcel Holtmann
2005-05-25 15:24 ` Ruben Jenster
2005-05-25 15:51 ` Marcel Holtmann
2005-05-25 20:34 ` Ruben Jenster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1116842913.30044.36.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox