Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#73236 - [bluez] Logitech MX Master 3 first connection doesn't work for ~30s

Attached to Project: Arch Linux
Opened by Aidan Dang (AidanGG) - Sunday, 02 January 2022, 21:10 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 19 February 2022, 16:19 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


Upon connecting with the Logitech MX Master 3 mouse via bluetooth, the mouse shows as connected but is unable to move the cursor for ~30s. Turning the mouse off and on again has it connect and working properly. The relevant journalctl entries are

bluetoothd[622]: profiles/input/hog-lib.c:set_report_cb() Error setting Report value: Unexpected error code
kernel: logitech-hidpp-device 0005:046D:B023.0008: Device not connected

This issue only appeared with the 5.62 release. The upstream bug report is I tested a fix in the comments found here and found it to solve the issue. The upstream bug report also suggest that reverting might also work, but I did not test this.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 19 February 2022, 16:19 GMT
Reason for closing:  Fixed
Comment by Pablo Klein-Bernard (asterion) - Tuesday, 04 January 2022, 19:30 GMT
I have this same issue with my Logitech MX Ergo bluetooth trackball. I have bluez 5.62-1 and Lenovo Thinkpad P1 with Wifi card: Intel Corporation Wireless-AC 9560 [Jefferson Peak] (rev 10).
I was able to solve it on my system (be careful!) by applying the patch from here:

Comment by Pablo Klein-Bernard (asterion) - Sunday, 16 January 2022, 21:30 GMT
I just tried upgrading to bluez 5.63-1 and this issue was not fixed.
Comment by loqs (loqs) - Thursday, 20 January 2022, 06:09 GMT
Please try building the package the attached PKGBUILD.diff applied that contains [1] that should fix this issues and [2] for  FS#73394 

Comment by Andreas Radke (AndyRTR) - Saturday, 19 February 2022, 09:11 GMT
Please try 5.63-2- it also has now debug symbols available for testing.
Comment by Aidan Dang (AidanGG) - Saturday, 19 February 2022, 13:04 GMT
Thank you Andreas, from my brief testing it appears that 5.63-2 from the testing repo fixes the error for me.