From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 210205] New: Repairing for btle-devices fail
Date: Sun, 15 Nov 2020 08:02:21 +0000 [thread overview]
Message-ID: <bug-210205-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=210205
Bug ID: 210205
Summary: Repairing for btle-devices fail
Product: Drivers
Version: 2.5
Kernel Version: Ubuntu 5.10.0-3-generic
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: marko.lavikainen@netkoti.fi
Regression: No
Created attachment 293677
--> https://bugzilla.kernel.org/attachment.cgi?id=293677&action=edit
Log from bluetoothctl
I have recently bought two Bluetooth devices:
- Microsoft Bluetooth Mouse 3600 (requires confirmation for pairing)
- Microsoft Surface Keyboard (requires passcode for pairing)
Both devices pair with the system and work fine. However, at random times
(maybe when idling) both devices change their mac-addresses to a new one.
This is a problem, because pairing disconnects, and bluez sees those devices as
new devices. Thus I need to manually repair them and... well, it should not be
like that.
I did make a bit crude python-script that communicates with 'bluetoothctl' and
repairs the mouse whenever it is discovered as a new device. But that does not
work with the keyboard because of the passcode requirement.
I attached some log from 'bluetoothctl'.
Is it possible to detect in the device driver that newly discovered device is
actually the same but with different mac-address and repair it automatically?
Bluetoothctl version is 5.53
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-11-15 8:02 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=bug-210205-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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