From: John Gruenenfelder <johng@as.arizona.edu>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] btsco - a few comments and a small .py script
Date: Fri, 19 Aug 2005 13:44:47 -0700 [thread overview]
Message-ID: <20050819204447.GA31631@as.arizona.edu> (raw)
In-Reply-To: <20050819193855.GA25514@uni-duesseldorf.de>
On Fri, Aug 19, 2005 at 09:38:55PM +0200, Andreas Beck wrote:
>Q: I have used the same bluetooth dongle on different machines or with
>different machine configurations (e.g. using windows). Now my device
>will refuse to pair again with the dongle.
>
>A: Remove the line in /var/lib/bluetooth/[my-bdaddr]/linkkeys that is
>corresponding to the device that doesn't want to pair. BlueZ thinks it
>is already paired, but the Link-Key does not match.
>
> I've seen a rather recent question that seems to be the same problem
> on bluez-users. However the hints there point to
> /etc/bluetooth/linkkeys - is this outdated or is this due to me using
> debian packages?
This was my experience. My device simply stopped working after I had used it
on another machine (same dongle though). I am also using the Debian packages
and there is no /etc/bluetooth/linkkeys.
For me, the problem manifested itself as "input/output error" messages when
trying most bluetooth commands or btsco. That's not a lot of help.
Eventually, somebody in my local users group tipped me off to the location of
the link keys as /var/lib/bluetooth and after deleting the offending files, my
headset could be paired again and it works now.
This seems, to me, to be a bug on both ends.
Bug 1) When you list the files in the Debian bluez packages,
/var/lib/bluetooth is not listed. This is a clear packaging bug as that
directory should definitely be listed therein, even if the package doesn't
actually ship with any files *in* that directory (they are program
generated).
Bug 2) When the bluez tools (hcitool I think) are told to remove a key, they
do not do so. That also made tracking down my problem harder. Thinking it
was a key issue, the command to delete the key was given, but it didn't seem
to do anything. Only manually deleting the file off the filesystem did the
trick.
--
--John Gruenenfelder Research Assistant, Steward Observatory, U of Arizona
johng@as.arizona.edu
Try Weasel Reader for PalmOS -- http://gutenpalm.sf.net
"This is the most fun I've had without being drenched in the blood
of my enemies!"
--Sam of Sam & Max
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-08-19 20:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 19:38 [Bluez-devel] btsco - a few comments and a small .py script Andreas Beck
2005-08-19 20:44 ` John Gruenenfelder [this message]
2005-08-20 20:13 ` Brad Midgley
2005-08-21 12:12 ` Andreas Beck
2005-08-21 19:26 ` Andreas Beck
2005-08-22 4:29 ` Brad Midgley
2005-08-22 12:09 ` Andreas Beck
2005-08-22 18:38 ` Andreas Beck
2005-08-22 18:53 ` [Bluez-devel] AGC and anti-noise patch for btsco kernel module Andreas Beck
2005-08-22 22:10 ` Brad Midgley
2005-08-23 15:04 ` Andreas Beck
2005-08-23 16:05 ` Andreas Beck
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=20050819204447.GA31631@as.arizona.edu \
--to=johng@as.arizona.edu \
--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