https://bugzilla.kernel.org/show_bug.cgi?id=199461 Szymon Janc (szymon.janc@xxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |szymon.janc@xxxxxxxxx --- Comment #2 from Szymon Janc (szymon.janc@xxxxxxxxx) --- Hi, So this is interesting issue as this mouse is using ID address during initial connection but distributes IRK key with different ID address (well, address is same, but address type is different, public instead of static random). This is causing clash on creating new object as (for historical reasons) BlueZ doesn't use address type in object path. Also, since this is undefined behavior from mouse (as it should use same ID address in connection and key distribution) to workaround this we would have to verify which address will mouse use after pairing. My guess is that it will use static random and that address type in IRK is bogus (bug in mouse). I'll try to prepare testing patch later this week. BTW you should report this issue to mouse manufacturer as well. -- You are receiving this mail because: You are the assignee for the bug.-- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
