Thanks, Anton-- I haven't tested the patch above, but it will probably work for me and you.
I am a bit concerned though that rolling back the change made by Ying Hsu of Chromium org. and signed-off by Luiz Augusto von Dentz of Intel might also be too broad. In other words, I suspect it is highly likely that: a) Ying Hsu's original change that broke our mice was too broad. b) Undoing Ying Hsu's change will also be too broad. and c) What likely will be correct is a more surgical/precise solution where some packets for controllers with LE audio should be reclassified while some packets for controllers with LE audio should not be reclassified. If I had to guess, given an Intel Bluetooth controller that supports LE audio (such as our Jefferson Peak controller), only the packets related to LE audio should be reclassified while the packets not related to LE audio (such as those related to mouse and keyboard input) should not be reclassified. In other words, undoing Ying Hsu's change might fix our mice but break some other devices (probably audio devices). It might not affect me, but it might affect someone we don't know who just happens to own a Bluetooth device that requires the reclassification of the packets. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100565 Title: kernel update broke Logitech G603 mouse over Bluetooth, other Bluetooth devices work fine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
