From: Berend De Schouwer <berend.de.schouwer@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: Lenovo keyboard
Date: Sun, 13 Dec 2015 09:20:56 +0200 [thread overview]
Message-ID: <1449991256.8150.3.camel@gmail.com> (raw)
In-Reply-To: <CA+RPYyX5b=QGdym1V0pFrU5kT_4HbTPeJF8piheUcp9MnOSYdQ@mail.gmail.com>
On Sat, 2015-12-12 at 17:06 +0100, chris wrote:
> Dear list,
>
> I've been consistently using a lenovo bluetooth keyboard since
> Bluez4.
> Since a recent (a month ago or so) upgrade (debian/stretch) it
> doesn't
> connect anymore.
> Neither does a Jabra Stealth earpiece which was doing fine a month
> ago.
>
> Even when it says conneced: yes, it isn't actually connected:
> the led of the keyboard indicates it isn't connected and there is no
> input.
I've got similar symptoms with 4 different bluetooth keyboards. One
Logitech, one Apple, one Kanex and one Astrum.
Pairing works, input fails.
At the same time, the kernel loops:
[ 1449.370904] Bluetooth: hci0 ACL packet for unknown connection handle
2
[ 1455.734779] Bluetooth: hci0 ACL packet for unknown connection handle
3
[ 1461.731976] Bluetooth: hci0 ACL packet for unknown connection handle
4
[ 1468.037014] Bluetooth: hci0 ACL packet for unknown connection handle
5
[ 1474.005517] Bluetooth: hci0 ACL packet for unknown connection handle
6
[ 1479.972716] Bluetooth: hci0 ACL packet for unknown connection handle
7
[ 1491.066637] Bluetooth: hci0 ACL packet for unknown connection handle
8
Eventually a working handle is found.
The Logitech is ancient, but the others are relatively new.
next prev parent reply other threads:[~2015-12-13 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 16:06 Lenovo keyboard chris
2015-12-13 7:20 ` Berend De Schouwer [this message]
2015-12-14 15:50 ` chris
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=1449991256.8150.3.camel@gmail.com \
--to=berend.de.schouwer@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.