Red Hat Bugzilla – Bug 1260623
Mouse reconnect takes long
Last modified: 2016-07-20 03:52:39 EDT
Description of problem:
Bluetooth mouse takes a long time to reconnect after, on or both:
* laptop suspend
* mouse powersave
The mouse does eventually reconnect, but this can take minutes, and the connection might have to be manually stopped and started in gnome-settings.
Version-Release number of selected component (if applicable):
It's been happening for a few kernel versions.
About 20% of the time.
Steps to Reproduce:
2. Pair Bluetooth mouse (and keyboard)
3. wait for suspend (or mouse powersave)
Mouse doesn't respond. The keyboard usually reconnects quickly.
Mouse and keyboard to reconnect in about a second.
When it happens, there are messages about "hci0 ACL packet for unknown connection", eg:
Sep 07 12:25:59 sieve-deschouwer-co-za kernel: Bluetooth: hci0 ACL packet for unknown connection handle 5
Sep 07 12:26:05 sieve-deschouwer-co-za kernel: Bluetooth: hci0 ACL packet for unknown connection handle 6
Sep 07 12:32:54 sieve-deschouwer-co-za kernel: Bluetooth: hci0 ACL packet for unknown connection handle 7
In this example, it took a few minutes.
New Info One:
This is hardware dependent.
Realtek rtl8723be (USB 0bda:b001) exhibits this bug. Reconnects take long (30 seconds?)
Kingston (Cambridge Silicon Radio, Ltd Bluetooth Dongle) (USB 0a12:0001) does not exhibit this bug. Reconnect is quick (< 1 second)
On the same motherboard / installation / kernel, just a different dongle. I can even duplicate it without logging in/out -- just swap the dongle.
New Info Two:
Fedora 23 has a patched driver for Realtek rtl8723be (see # 1208375) so I assume the patched driver is not 100% OK. Should likely be re-assigned to kernel.
New Info Three:
This appears to only be a problem if there's more than one bluetooth device connected. I haven't been able to duplicate it with just one device connected.
I'm not 100% confident of this statement.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
I can still reproduce this in Fedora 24, so I am re-opening this as the automated message suggests.