From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-bluetooth@vger.kernel.org
Subject: have to re-pair mouse every few hours
Date: Sat, 30 Nov 2013 15:37:36 -0500 [thread overview]
Message-ID: <1385843856.12122.5.camel@pc.interlinx.bc.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
Hi,
I'm using a Microsoft Sculpt Touch Mouse on a Fedora 19 machine
(kernel-3.11.9-200.fc19.x86_64 and bluez-4.101-9.fc19.x86_64) with a:
Bus 002 Device 019: ID 0a5c:2148 Broadcom Corp. BCM92046DG-CL1ROM Bluetooth 2.1 Adapter
bluetooth adapter. This exact same configuration worked for months just
fine with a Logitech bluetooth mouse. But sadly that mouse was crap
(second one to fail within the warranty period of one of them) so
replaced it with this MS one.
The problem with this MS mouse is that it just goes AWOL and needs to be
delete and re-paired with the machine every few hours. Typically it's
after I have gotten up from the computer and have come back to it. But
I have also had it just happen while using it.
When this happens, the messages log reports messages such as:
Nov 30 12:42:03 pc kernel: [2500032.028982] Bluetooth: Unexpected continuation frame (len 0)
Nov 30 12:42:03 pc kernel: [2500032.115027] Bluetooth: Unexpected continuation frame (len 0)
Any ideas what the problem might be here?
Cheers,
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2013-11-30 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 20:37 Brian J. Murrell [this message]
2013-12-01 22:28 ` have to re-pair mouse every few hours Bastien Nocera
2013-12-01 22:36 ` Brian J. Murrell
2013-12-01 22:38 ` Bastien Nocera
2013-12-01 22:44 ` Brian J. Murrell
2013-12-02 22:35 ` Brian J. Murrell
2013-12-03 21:43 ` have to re-pair mouse every few hours (update: mouse needs periodic authorization?) Brian J. Murrell
2013-12-03 23:12 ` Bastien Nocera
2013-12-04 0:06 ` Brian J. Murrell
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=1385843856.12122.5.camel@pc.interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox