On 15/10/2020 01:03, Peter Robinson wrote:
A new proposed blocker bug showed up today:
https://bugzilla.redhat.com/show_bug.cgi?id=1874082
the issue is that if you have a bluetooth mouse working, then suspend
the system, when you resume the bluetooth mouse will not be working any
more. You have to go into the GNOME Bluetooth settings applet to get it
to work again.
So far we have two reports, but they happened to have the exact same
mouse. Can other folks who have bluetooth mice (and even, perhaps,
other bluetooth hardware - keyboards, headsets?) - ideally different
ones! - please test this and report their findings either here or to
the bug? It's important to know what range of hardware this affects.
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.
I would second that observation.
I've got a Logitech M557 BT Mouse. On an Acer Laptop it will not auto reconnect when
the system is rebooted. I have to issue a "bluetoothctl connect" command. However,
when the same mouse is used on my HP Tower system it reconnects just fine. This
observation is on an F32 KDE spin.
---
The key to getting good answers is to ask good questions.
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
