Description of problem: Since kernel 4.19.15-300.fc29 bluetooth mouse has not worked. Last working kernel was 4.19.14-300.fc29, all subsequent kernels have broken bluetooth HIDP. Tested on 3 different machines with FC29 and different hardware and similar failed outcomes. Connection and immediate disconnections, repeat. No mouse movement. Bluetooth is working (i.e. file transfers to/from phone), only HIDP is broken. Version-Release number of selected component (if applicable): FC29 How reproducible: Always Steps to Reproduce: 1. Boot w/ kernel 4.19.14-300.fc29. Scan and connect a bluetooth mouse. Profit. 2. Boot w/ kernel 4.19.15-300.fc29 or later. Scan and connect a bluetooth mouse. It will immediately disconnect, reconnect, disconnect, etc. Fail. Actual results: The "Bluetooth: HIDP (Human Interface Emulation) ver 1.2"/"Bluetooth: HIDP socket layer initialized" is not automatically loaded. When the hidp.ko is manually loaded, no change in behavior. The bluetooth mouse still does not work: journalctl -f: Jan 28 13:36:57 HostName bluetoothd[1359]: HUP or ERR on socket: Connection reset by peer (104) Jan 28 13:37:22 HostName bluetoothd[1359]: HUP or ERR on socket: Connection timed out (110) ... Jan 28 13:39:08 HostName bluetoothd[1359]: getpeername: Transport endpoint is not connected (107) ... Jan 28 13:39:29 HostName bluetoothd[1359]: HUP or ERR on socket: Connection timed out (110) Jan 28 13:39:36 HostName bluetoothd[1359]: getpeername: Transport endpoint is not connected (107) ... Jan 28 13:40:45 HostName bluetoothd[1359]: HUP or ERR on socket: Connection timed out (110) Expected results: Working HIDP (bluetooth mouse) as has been the norm for years and previous kernels. Additional info: https://forums.fedoraforum.org/showthread.php?320530-Kernel-4-19-15-300-fc29-broke-bluetooth-HIDP https://ask.fedoraproject.org/en/question/132475/kernel-41915-300fc29-broke-bluetooth-hidp/ Thanks!
This doesn't appear to be a problem with the hidapi package but with the kernel. Reassigning.
Found another bug report with similar findings: 1671123
Does anyone have a status on this? Many kernel releases later and it's *STILL* broken. Thanks.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 29 kernel bugs. Fedora XX has now been rebased to 5.0.6 Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 30, and are still experiencing this issue, please change the version to Fedora 30. If you experience different issues, please open a new bug report for those.
Tested on 5.1.9-300.fc30.x86_64. Still a problem, but I don't see the kernel related kernel messages anymore. Symptoms: Logitec bluetooth travel mouse, connects, works as long as mouse movement doesn't stop. When it sits idle for 2-3 seconds, further mouse movements don't result in pointer motion. However, moving the mouse wheel "wakes" the mouse up and pointer motion is reestablished. I've fiddled around with 'powertop' extensively without any success. I suspect this is driver-related as my bluetooth controller is in the newer wireless network card: 6f:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) Thank you.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.2.9-200.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
This bug is still present, as of 5.2.11-200.fc30.x86_64. Pertains to bluetooth adapter BT ID 8087:0025 Intel Corp. that is included with 6f:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29). Symptoms: Bluetooth mouse connects and works nominally as long as motion is constant. When mouse pointer sits idle for ~ 2 seconds, further pointer motion does not work. However, movement of the mouse wheel will subsequently enable mouse motion again, until the next time motion is idle. Rinse, repeat. Bluetooth mouse works as expected with an external usb-bt adapter (no idle timeouts). --------------------------------------- Sep 04 16:56:43 hostname kernel: usb 1-14: new full-speed USB device number 10 using xhci_hcd Sep 04 16:56:43 hostname kernel: usb 1-14: New USB device found, idVendor=8087, idProduct=0025, bcdDevice= 0.02 Sep 04 16:56:43 hostname kernel: usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Sep 04 16:56:43 hostname kernel: Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015 Sep 04 16:56:43 hostname kernel: Bluetooth: hci0: Device revision is 2 Sep 04 16:56:43 hostname kernel: Bluetooth: hci0: Secure boot is enabled Sep 04 16:56:43 hostname kernel: Bluetooth: hci0: OTP lock is enabled Sep 04 16:56:43 hostname kernel: Bluetooth: hci0: API lock is enabled Sep 04 16:56:43 hostname kernel: Bluetooth: hci0: Debug lock is disabled Sep 04 16:56:43 hostname kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Sep 04 16:56:43 hostname kernel: Bluetooth: hci0: Found device firmware: intel/ibt-18-16-1.sfi --------------------------------------- Bluetooth Mouse: --------------------------------------- Sep 04 16:58:06 hostname bluetoothd[1465]: Can't get HIDP connection info Sep 04 16:58:06 hostname kernel: hid-generic 0005:046D:B002.0009: unknown main item tag 0x0 Sep 04 16:58:06 hostname kernel: input: Bluetooth Travel Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:046D:B002.0009/input/input46 Sep 04 16:58:06 hostname kernel: hid-generic 0005:046D:B002.0009: input,hidraw5: BLUETOOTH HID v48.09 Mouse [Bluetooth Travel Mouse] on 18:1d:ea:20:96:48 Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[1915]: (II) config/udev: Adding input device Bluetooth Travel Mouse (/dev/input/mouse3) Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[1915]: (II) No input driver specified, ignoring this device. Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[1915]: (II) This device may have been added with another device file. Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) config/udev: Adding input device Bluetooth Travel Mouse (/dev/input/mouse3) Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) No input driver specified, ignoring this device. Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) This device may have been added with another device file. Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) config/udev: Adding input device Bluetooth Travel Mouse (/dev/input/event26) Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (**) Bluetooth Travel Mouse: Applying InputClass "evdev pointer catchall" Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (**) Bluetooth Travel Mouse: Applying InputClass "libinput pointer catchall" Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) Using input driver 'libinput' for 'Bluetooth Travel Mouse' Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[1915]: (II) config/udev: Adding input device Bluetooth Travel Mouse (/dev/input/event26) Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[1915]: (**) Bluetooth Travel Mouse: Applying InputClass "evdev pointer catchall" Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[1915]: (**) Bluetooth Travel Mouse: Applying InputClass "libinput pointer catchall" Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[1915]: (II) Using input driver 'libinput' for 'Bluetooth Travel Mouse' Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) systemd-logind: got fd for /dev/input/event26 13:90 fd 122 paused 0 Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (**) Bluetooth Travel Mouse: always reports core events Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (**) Option "Device" "/dev/input/event26" Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (**) Option "_source" "server/udev" Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[1915]: (II) systemd-logind: got fd for /dev/input/event26 13:90 fd 30 paused 1 Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[1915]: (II) systemd-logind: releasing fd for 13:90 Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) event26 - Bluetooth Travel Mouse: is tagged by udev as: Mouse Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) event26 - Bluetooth Travel Mouse: device is a pointer Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) event26 - Bluetooth Travel Mouse: device removed Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-14/1-14:1.0/bluetooth/hci0/hci0:256/0005:046D:B002.0009/input/input46/event26" Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) XINPUT: Adding extended input device "Bluetooth Travel Mouse" (type: MOUSE, id 22) Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (**) Option "AccelerationScheme" "none" Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (**) Bluetooth Travel Mouse: (accel) selected scheme none/0 Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (**) Bluetooth Travel Mouse: (accel) acceleration factor: 2.000 Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (**) Bluetooth Travel Mouse: (accel) acceleration threshold: 4 Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) event26 - Bluetooth Travel Mouse: is tagged by udev as: Mouse Sep 04 16:58:06 hostname /usr/libexec/gdm-x-session[2433]: (II) event26 - Bluetooth Travel Mouse: device is a pointer --------------------------------------- No log entries related to the frozen pointer. Thanks.
This bug is still present, as of 5.3.7-200.fc30.x86_64. Pertains to bluetooth adapter BT ID 8087:0025 Intel Corp. that is included with 6f:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29). Symptoms: Bluetooth mouse connects and works nominally as long as motion is constant. When mouse pointer sits idle for ~ 2 seconds, further pointer motion does not work. However, movement of the mouse wheel (or button clicks) will subsequently enable mouse motion again, until the next time motion is idle. Rinse, repeat. Bluetooth mouse works as expected with an external usb-bt adapter (no idle timeouts).
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those.
Last working kernel version, same hardware, 4.9.14-300.fc29. This bug is still present, as of 5.5.8-200.fc31.x86_64. Pertains to bluetooth adapter BT ID 8087:0025 Intel Corp. that is included with 6f:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29). Logitech Bluetooth Mouse M-RBB93 852555-0000. Symptoms: Bluetooth mouse connects and works nominally as long as motion is constant. When mouse pointer sits idle for ~ 2 seconds, further pointer motion does not work. However, movement of the mouse wheel (or button clicks) will subsequently enable mouse motion again, until the next time motion is idle. Rinse, repeat. Bluetooth mouse works as expected with an external usb-bt adapter (no idle timeouts).
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.