The problem here is it could be very hardware/firmware dependent, not just for the mouse but the controller as well. I have seen issues across a bunch of BT devices that don't happen on others and that can be very out of our control.

On 10/14/20 11:33 AM, Adam Williamson wrote: Just tested with the KDE compose and some bluetooth headphones. After a suspend / resume (closed then opened laptop lid), I had to manually reconnect the headphones. I'm assuming that's not the expected behavior.

On 10/14/20 3:13 PM, Peter Robinson wrote: [Snip] They were blinking like they were trying to reconnect. The suspend was only a handful of seconds. If I get a chance, I'll try again with the Gnome compose and see if any of the log messages match the ones in the bug report.

On Wed, Oct 14, 2020 at 9:21 PM Adam Williamson <adamwill(a)fedoraproject.org&gt; wrote: AFAICT that's not fixing a recent regression thought, it seems more of an enhancement for Linux BT audio support as a whole. I suspect we'll have a new bluez release in the next day or so because of the just announced BleedingTooth [1] vulnerability. P [1] https://lwn.net/Articles/834297/

On 10/14/20 3:19 PM, Brandon Nielsen wrote: [Snip] Just tried on Gnome, essentially the same behavior. Based on the Bluez discussion elsewhere in this thread I'm going to assume this is just the expected current behavior. So I cannot reproduce the potential blocker with anything convenient to me.

On Thu, 2020-10-15 at 13:13 -0400, murph nj wrote: Nope, that's very helpful already! Thanks. We really just need broad data like this, to figure out whether it's affecting all or a wide range of hardware, or if it's more of a limited bug. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net

Hello: I've noticed a problem attaching a bluetooth mouse. (or enabling bluetooth at all) I have a laptop that I don't depend on, and use for testing, or playing around. It's a converted Chromebook, an Acer C710. In the past, I've used bluetooth, primarily for a mouse. Converted it to use the rawhide branch a while ago, and everything seemed OK. My use case for it has changed, so it has spent more time plugged into devices, including a trackball, so I'm not sure exactly when this change happened. At some point, the bluetooth mouse stopped working, and I was unable to turn on the bluetooth adapter on the laptop at all. I figured that it was my fault, I had done some questionable removals of packages to get things to upgrade. No problem, I'll wipe and reload, and get it working. While booting off the F33 USB drive, no problem, I was able to use the mouse. Installed, and booted up the system, same. After I did a full system upgrade, it is back to not working again. If I boot from an older kernel (the 5.8.15 from the install image) no problem. If I boot from the 5.10.10, the bluetooth module does not work. I've seen the same results with KDE, gnome, and XFCE, so I'm pretty sure it's not the DE. I get the following: dmesg | grep hci0 [ 11.031856 ] Bluetooth: hci0: don't support firmware rome 0x11020000 Like the following shows: https://bugzilla.kernel.org/show_bug.cgi?id=210681 Not sure where else to go from here, wait until the fix is committed in the kernel? If a bug report needs to be made, if someone could point me in the right direction. One irony of this is that I ran the tests for the 5.10 kernel, but never tried to hook up a BT mouse, so I didn't think to mention it. Thanks, --murph