Since I upgraded from F35 to Rawhide this week, my bluetooth mouse takes quite some time to start working after I boot or resume from suspend. It seems to take about 30 seconds from the time I can use the keyboard or trackpad fine. In the journal, I see these messages at the time it starts working: Nov 03 10:59:41 xps13k.happyassassin.net kernel: logitech-hidpp-device 0005:046D:B023.000A: HID++ 4.5 device connected. Nov 03 10:59:42 xps13k.happyassassin.net upowerd[1488]: treating change event as add on /sys/devices/virtual/misc/uhid/0005:046D:B023.000A/power_supply/hidpp_battery_0 Nov 03 10:59:42 xps13k.happyassassin.net kernel: input: Logitech Wireless Mouse MX Master 3 as /devices/virtual/misc/uhid/0005:046D:B023.000A/input/input39 Nov 03 10:59:42 xps13k.happyassassin.net kernel: logitech-hidpp-device 0005:046D:B023.000A: input,hidraw8: BLUETOOTH HID v0.15 Keyboard [Logitech Wireless Mouse MX Master 3] on 9c:b6:d0:d0:d1:be Nov 03 10:59:42 xps13k.happyassassin.net systemd-logind[1042]: Watching system buttons on /dev/input/event28 (Logitech Wireless Mouse MX Master 3) The mouse is, as the messages say, an MX Master 3. The kernel module in use seems to be hid_logitech_hidpp . In the upgrade from F35 to Rawhide, the kernel went from 5.15.0-0.rc6.47.fc36.x86_64 - I was actually running a Rawhide kernel on F35, I'd forgotten about that - to 5.15.0-0.rc7.53.fc36.x86_64 . bluez went from bluez-5.61-1.fc35.x86_64 to bluez-5.62-1.fc36.x86_64 . I'll try booting with older kernel and older bluez and see if it changes things.
Huh, it seems to be bluez that's the culprit. Booting with an older kernel doesn't help, but booting with bluez 5.61 does. Booting that way, I get two sets of those messages, with more context, and they start earlier: Nov 03 11:20:27 xps13k.happyassassin.net bluetoothd[1086]: profiles/input/hog-lib.c:report_value_cb() bt_uhid_send: Invalid argument (22) Nov 03 11:20:27 xps13k.happyassassin.net bluetoothd[1086]: profiles/input/hog-lib.c:report_value_cb() bt_uhid_send: Invalid argument (22) Nov 03 11:20:27 xps13k.happyassassin.net bluetoothd[1086]: profiles/input/hog-lib.c:report_value_cb() bt_uhid_send: Invalid argument (22) Nov 03 11:20:27 xps13k.happyassassin.net bluetoothd[1086]: profiles/input/hog-lib.c:report_value_cb() bt_uhid_send: Invalid argument (22) Nov 03 11:20:27 xps13k.happyassassin.net bluetoothd[1086]: profiles/input/hog-lib.c:report_value_cb() bt_uhid_send: Invalid argument (22) Nov 03 11:20:27 xps13k.happyassassin.net bluetoothd[1086]: profiles/input/hog-lib.c:report_value_cb() bt_uhid_send: Invalid argument (22) Nov 03 11:20:27 xps13k.happyassassin.net bluetoothd[1086]: profiles/input/hog-lib.c:report_value_cb() bt_uhid_send: Invalid argument (22) Nov 03 11:20:27 xps13k.happyassassin.net kernel: input: MX Master 3 Keyboard as /devices/virtual/misc/uhid/0005:046D:B023.0009/input/input36 Nov 03 11:20:27 xps13k.happyassassin.net kernel: input: MX Master 3 Mouse as /devices/virtual/misc/uhid/0005:046D:B023.0009/input/input37 Nov 03 11:20:27 xps13k.happyassassin.net kernel: hid-generic 0005:046D:B023.0009: input,hidraw8: BLUETOOTH HID v0.15 Keyboard [MX Master 3] on 9c:b6:d0:d0:d1:be Nov 03 11:20:27 xps13k.happyassassin.net kernel: logitech-hidpp-device 0005:046D:B023.0009: HID++ 4.5 device connected. Nov 03 11:20:27 xps13k.happyassassin.net kernel: input: Logitech Wireless Mouse MX Master 3 as /devices/virtual/misc/uhid/0005:046D:B023.0009/input/input39 Nov 03 11:20:27 xps13k.happyassassin.net kernel: logitech-hidpp-device 0005:046D:B023.0009: input,hidraw8: BLUETOOTH HID v0.15 Keyboard [Logitech Wireless Mouse MX Master 3] on 9c:b6:d0:d0:d1:be Nov 03 11:20:27 xps13k.happyassassin.net gnome-shell[1504]: Could not open device /dev/input/event29: Could not get device info for path /dev/input/event29: No such file or directory Nov 03 11:20:27 xps13k.happyassassin.net gnome-shell[1504]: Could not open device /dev/input/event28: GDBus.Error:System.Error.ENODEV: No such device Nov 03 11:20:27 xps13k.happyassassin.net upowerd[1564]: treating change event as add on /sys/devices/virtual/misc/uhid/0005:046D:B023.0009/power_supply/hidpp_battery_0 Nov 03 11:20:27 xps13k.happyassassin.net systemd-logind[1111]: Watching system buttons on /dev/input/event28 (Logitech Wireless Mouse MX Master 3) ... Nov 03 11:20:59 xps13k.happyassassin.net kernel: logitech-hidpp-device 0005:046D:B023.000A: HID++ 4.5 device connected. Nov 03 11:20:59 xps13k.happyassassin.net upowerd[1564]: treating change event as add on /sys/devices/virtual/misc/uhid/0005:046D:B023.000A/power_supply/hidpp_battery_1 Nov 03 11:21:00 xps13k.happyassassin.net kernel: input: Logitech Wireless Mouse MX Master 3 as /devices/virtual/misc/uhid/0005:046D:B023.000A/input/input40 Nov 03 11:21:00 xps13k.happyassassin.net kernel: logitech-hidpp-device 0005:046D:B023.000A: input,hidraw8: BLUETOOTH HID v0.15 Keyboard [Logitech Wireless Mouse MX Master 3] on 9c:b6:d0:d0:d1:be Nov 03 11:21:00 xps13k.happyassassin.net systemd-logind[1111]: Watching system buttons on /dev/input/event28 (Logitech Wireless Mouse MX Master 3) so it almost seems like it gets initialized twice, the first time messily, the second time more quietly. If anything it's like with 5.62 the earlier, messier startup has gone away and we have only the later, cleaner one.
Seeing something very similar on Fedora 35, kernel 5.14.16-301.fc35.x86_64, bluez 5.62-1.fc35. Also on another laptop, that one on Fedora 34, same kernel version (F34 package), same bluez version (again same package). This seems to correlate with the upgrade to bluez 5.62 on both systems. Mouse is also a MX Master 3. In my case the pattern is that the first time *after a boot* that I try to connect this mouse to the laptop (turn it on or switch it to that laptop using the connection switcher on the underside of the mouse), I get this pattern of messages: Nov 06 18:05:38 greebo systemd[2471]: Reached target Bluetooth. Nov 06 18:05:38 greebo kernel: input: MX Master 3 Keyboard as /devices/virtual/misc/uhid/0005:046D:B023.0005/input/input26 Nov 06 18:05:38 greebo kernel: input: MX Master 3 Mouse as /devices/virtual/misc/uhid/0005:046D:B023.0005/input/input27 Nov 06 18:05:38 greebo kernel: hid-generic 0005:046D:B023.0005: input,hidraw3: BLUETOOTH HID v0.15 Keyboard [MX Master 3] on <address> Nov 06 18:05:38 greebo bluetoothd[1492]: profiles/input/hog-lib.c:set_report_cb() Error setting Report value: Unexpected error code Nov 06 18:05:38 greebo kernel: logitech-hidpp-device 0005:046D:B023.0005: Device not connected Nov 06 18:05:38 greebo gnome-shell[2607]: Could not open device /dev/input/event23: Could not get device info for path /dev/input/event23: No such file or directory Nov 06 18:05:38 greebo gnome-shell[2607]: Could not open device /dev/input/event24: Could not get device info for path /dev/input/event24: No such file or directory Mouse shows as connected in the GNOME system menu, but not responding. Then I turn the mouse off, wait a couple of seconds, turn it back on: Nov 06 18:06:35 greebo kernel: logitech-hidpp-device 0005:046D:B023.0006: HID++ 4.5 device connected. Nov 06 18:06:35 greebo upowerd[1517]: treating change event as add on /sys/devices/virtual/misc/uhid/0005:046D:B023.0006/power_supply/hidpp_battery_0 Nov 06 18:06:35 greebo kernel: input: Logitech Wireless Mouse MX Master 3 as /devices/virtual/misc/uhid/0005:046D:B023.0006/input/input29 Nov 06 18:06:35 greebo kernel: logitech-hidpp-device 0005:046D:B023.0006: input,hidraw3: BLUETOOTH HID v0.15 Keyboard [Logitech Wireless Mouse MX Master 3] on <address> Nov 06 18:06:35 greebo systemd-logind[1508]: Watching system buttons on /dev/input/event23 (Logitech Wireless Mouse MX Master 3) At this point the mouse works. Turn mouse back off, suspend laptop for a short time, resume, turn mouse on: Nov 06 18:13:07 greebo kernel: logitech-hidpp-device 0005:046D:B023.0008: HID++ 4.5 device connected. Nov 06 18:13:07 greebo upowerd[1517]: treating change event as add on /sys/devices/virtual/misc/uhid/0005:046D:B023.0008/power_supply/hidpp_battery_2 Nov 06 18:13:07 greebo kernel: input: Logitech Wireless Mouse MX Master 3 as /devices/virtual/misc/uhid/0005:046D:B023.0008/input/input31 Nov 06 18:13:07 greebo kernel: logitech-hidpp-device 0005:046D:B023.0008: input,hidraw3: BLUETOOTH HID v0.15 Keyboard [Logitech Wireless Mouse MX Master 3] on <address> Nov 06 18:13:07 greebo systemd-logind[1508]: Watching system buttons on /dev/input/event23 (Logitech Wireless Mouse MX Master 3) mouse works again on 1st connection after resume. Two things I notice about the logs on that first, unsuccessful connect: Nov 06 18:05:38 greebo systemd[2471]: Reached target Bluetooth. ← systemd only reaches this when I connect the first Bluetooth device? Also, no "logitech-hidpp-device 0005:046D:B023.0006: HID++ 4.5 device connected." line. Nov 06 18:05:38 greebo kernel: hid-generic 0005:046D:B023.0005: input,hidraw3: BLUETOOTH HID v0.15 Keyboard [MX Master 3] on <address> ← hid-generic instead of, in the successful attempts, logitech-hidpp-device.
I experience exactly the same behaviour as Dimitris on a fresh installation of Fedora 35 with a Logitech MX Master 3 mouse. Even after waiting a couple of minutes the mouse doesn't work. The workarounds mentioned by Dimitris do work perfectly however (use power or device switch after initial connection to let the mouse reconnect). This is a known bug with bluez 5.62 and seems to affect especially the Logitech MX Master series mouses: https://github.com/bluez/bluez/issues/220 I think it would be great to have this bug and the easy workaround mentioned on https://fedoraproject.org/wiki/Common_F35_bugs
Oh, dang, sorry, I meant to block the update for F35 but forgot. :/ I'll try and do something about this tomorrow. It might be possible to fix/workaround it, rather than documenting it.
FEDORA-2021-92993b2072 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-92993b2072
Adrian: Dimitris: can you please try the update and see if it helps? Thanks!
Adam, will do ASAP. BTW F34 is also affected.
Adam: I downloaded and manually updated the bluez packages on my Fedora 35 installation from https://koji.fedoraproject.org/koji/buildinfo?buildID=1853311 After rebooting the machine MX Master 3 mouse now successfully works fully automatic without having to reconnect it. I tested these scenarios: - Reboot machine - Turn Bluetooth off and on again via Gnome - Suspend machine and wake up again Thank you for the quick fix!
FEDORA-2021-92993b2072 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-92993b2072` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-92993b2072 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Same here, LGTM
FEDORA-2021-92993b2072 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.