* [Bug 210205] New: Repairing for btle-devices fail
@ 2020-11-15 8:02 bugzilla-daemon
0 siblings, 0 replies; only message in thread
From: bugzilla-daemon @ 2020-11-15 8:02 UTC (permalink / raw)
To: linux-bluetooth
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-11-15 8:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-11-15 8:02 [Bug 210205] New: Repairing for btle-devices fail bugzilla-daemon
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).