Bug 2323758 - Bluetooth Logitech MX Master 3 slow to reconnect after sleeping
Summary: Bluetooth Logitech MX Master 3 slow to reconnect after sleeping
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: bluez
Version: 43
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gopal krishna tiwari
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-05 00:08 UTC by Chris Adams
Modified: 2025-12-04 20:48 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-04 20:48:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chris Adams 2024-11-05 00:08:18 UTC
I have a Logitech MX Master 3 mouse, connecting over Bluetooth. After upgrading to Fedora 41 with bluez-5.78, it takes about 5 seconds to reconnect and be usable after it goes to sleep for being idle. The mouse's LED lights up solid during that time. On a Fedora 39 test, it looks like this behavior started with bluez version 5.77 - 5.76 works fine. I saw version 5.79 in F41 updates-testing and tried that, but still get the same 5 second delay problem.

I seem to remember a previous issue with bluez+MX Master 3.

Current system is F41 x86_64, all current updates plus bluez 5.79 from updates-testing.

Reproducible: Always

Comment 1 Peter Robinson 2024-11-05 07:54:34 UTC
It's unlikely to be bluez

Please include:
* kernel version
* linux-firmware version
* bluez version
* type of bluetooth controller (lsusb| grep -i blue)
* the bluetooth devices (make and model) that you are trying to pair

Comment 2 Chris Adams 2024-11-05 21:59:28 UTC
Well, it reliably happens with bluez-5.77 (and newer) and not with bluez-5.76 on F39. It takes 30 minutes to test, I guess that's how long the mouse waits before going into a sleep mode.

kernel-6.11.5-300.fc41.x86_64
linux-firmware-20241017-2.fc41.noarch
bluez-5.79-1.fc41.x86_64

Bus 003 Device 002: ID 8087:0029 Intel Corp. AX200 Bluetooth

Logitech MX Master 3 mouse

[177972.164138] input: MX Master 3 as /devices/virtual/misc/uhid/0005:046D:B023.0023/input/input53
[177972.164428] logitech-hidpp-device 0005:046D:B023.0023: input,hidraw4: BLUETOOTH HID v0.13 Keyboard [MX Master 3] on 50:e0:85:be:97:d5

Comment 3 Chris Adams 2024-11-07 01:32:30 UTC
I was going to build 5.76 for F41, but saw there was already a build in koji, so I downgraded to bluez-5.76-2.fc41, and that works fine. No noticeable delay reconnecting after the mouse has been idle for a while

Comment 4 Peter Robinson 2024-11-25 12:46:30 UTC
So I believe this has been fixed with the kernel-6.11.10-300.fc41 update

Comment 5 Chris Adams 2024-11-27 01:39:43 UTC
It seems to be fixed, yes. Using:

kernel-6.11.10-300.fc41.x86_64
bluez-5.79-1.fc41.x86_64

Thanks

Comment 6 Chris Adams 2024-11-28 16:59:37 UTC
Actually, scratch that - if anything, it has gotten worse (takes even longer to re-sync after mouse idle). Maybe it's after a system suspend/resume cycle (so that's why I didn't see it immediately)?

Comment 7 Peter Robinson 2025-04-03 09:23:30 UTC
Is this still an issue?

Comment 8 Chris Adams 2025-04-04 23:03:12 UTC
It doesn't seem to be happening all the time, but it still happens (sometimes taking 10+ seconds to start working again). That's with:

kernel-6.13.9-200.fc41.x86_64
bluez-5.79-1.fc41.x86_64

Downgrading bluez packages to 5.76-2.fc41 makes it work again.

Comment 9 Peter Robinson 2025-04-06 13:22:07 UTC
Can you test this with updates-testing

https://bodhi.fedoraproject.org/updates/FEDORA-2025-99ba5bbe50

Comment 10 Chris Adams 2025-04-07 17:51:37 UTC
Gave it a try, unfortunately doesn't seem to fix it. It works okay after a boot (maybe slightly slower to come back after idle), but after a suspend/resume cycle and then letting the system sit for a while (hour or so), the mouse takes a long time to work. The Bluetooth tray icon (MATE desktop) turns green, so it's connected, but it won't work for 10+ seconds.

Comment 11 Chris Adams 2025-10-07 14:19:14 UTC
This is still an issue with:

kernel-6.16.9-100.fc41.x86_64
bluez-5.84-2.fc41.x86_64

Comment 12 Chris Adams 2025-11-06 20:33:00 UTC
Upgraded to Fedora 43 and this is still an issue.

Comment 13 Chris Adams 2025-12-04 20:48:23 UTC
I think this is fixed in bluez-5.85-1.fc43


Note You need to log in before you can comment on or make changes to this bug.