From: Chris Carlin <carlin@jlab.org>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Mysterious regression: Link authentication time out
Date: Tue, 15 Apr 2008 16:50:39 -0400 [thread overview]
Message-ID: <4805151F.1010309@jlab.org> (raw)
I've been using three Dell branded bluetooth keyboards (P/N DH953) just fine for
months. Now they've simultaneously stopped working, and system logs have the
following repeated every time the keyboard tries to connect:
Apr 15 16:16:14 [hcid] Link authentication failed: Connection timed out (110)
Apr 15 16:16:14 [hcid] link_key_request (sba=***, dba=***)
with *** replaced by the respective addresses.
These are three completely independent keyboards miles apart. The
computers use various brands and chipsets in their bluetooth dongles, which themselves are variety of combinations of bluetooth version and class, and which continue to work flawlessly with mice, A2DP, etc. They run Bluez versions between 3.28 and 3.30, Linux kernels 2.6.23/4
As I said, all three keyboards had been working fine for six months to a year--so good was my experience that I kept buying new ones and recommending them. Yet despite this record all three stopped working within a single week. I didn't
make any changes to the systems during that time--no upgrades, no bluez
configuration changes, nothing.
I've replaced batteries, deleted and re-paired, restarted, re-pined, and
everything else but with no luck.
Anyone have any idea what might be going on here? Has there been a worldwide
death of these keyboards?
~Chris
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2008-04-15 20:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4805151F.1010309@jlab.org \
--to=carlin@jlab.org \
--cc=bluez-users@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;
as well as URLs for NNTP newsgroup(s).