Bluetooth mouse in disconnection loops

aleritty · 2024-02-15 08:32:43

Hi,
I’ve recently encountering a problem with my Logitech MX Master 2 bluetooth mouse.
I've a Lenovo Thinkpad p14s running Linux 6.7.0-0-MANJARO x86_64.

This mouse worked flawlessly for more than a year with my system using the bluetooth connection, but now, after probably some updates, I’m having problems.

Basically when I turn on my laptop the mouse starts connecting and immediately disconnecting in an infinite loop.
If I turn on the laptop (with the mouse off), this happens as soon as I turn on the mouse.
The only solution is to remove the device and re-pair it.

After this procedure the device works perfectly.

If I turn off the Bluetooth of the laptop (or the mouse) and then turn it on again, it connects and works without any problem.
Apparently this only happens on cold boots (and this is the reason I'm posting in this category)

I already tried this solution that seems do be similar:
https://wiki.archlinux.org/title/blueto … 2%2C%20etc

But without success.

Journalctl show this:

bluetoothd[618]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error
bluetoothd[618]: profiles/input/hog-lib.c:info_read_cb() HID Information read failed: Request attribute has encountered an unlikely error
bluetoothd[618]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[618]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[618]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[618]: profiles/input/hog-lib.c:report_reference_cb() Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
bluetoothd[618]: profiles/input/hog-lib.c:proto_mode_read_cb() Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error

Can you please help me diagnose and solve the problem?

Thank you

Last edited by aleritty (2024-02-15 14:05:35)

aleritty · 2024-02-16 06:44:40

Maybe this bug can be related:

https://github.com/bluez/bluez/issues/745

d_fajardo · 2024-02-16 08:19:18

I've a Lenovo Thinkpad p14s running Linux 6.7.0-0-MANJARO x86_64

Manjaro is not supported here and probably would be difficult for us to provide an answer as Arch uses different kernel.

aleritty · 2024-02-16 08:20:02

I know, but In my opinion this is a bluez bug, not directly related to the distro.

d_fajardo · 2024-02-16 08:22:41

I know, but In my opinion this is a bluez bug, not directly related to the distro.

Then your question is answered. Manjaro is not Archlinux.

aleritty · 2024-02-16 08:23:35

My question is about diagnosing and solving this bug, therefore is not answered yet.

d_fajardo · 2024-02-16 08:29:30

My question is about diagnosing and solving this bug, therefore is not answered yet.

Why not then ask it in the Manjaro forum? The answer is we can't answer your question as you're using a different machine. Why not ask Manjaro forum how to diagnose it?

aleritty · 2024-02-16 08:53:54

I already did it, but the Arch community is much larger and I will give more opportunities posting also here.
I repeat: this issue can happen in arch, therefore is also relevant to arch users.

Now, please, let's stay on topic and discuss of the issue (if you want to help. of course).

d_fajardo · 2024-02-16 09:02:08

if you want to help. of course

It's really rather simple. You said you ran into problems when you updated to 6.7.0-0-MANJARO x86_64 but Arch is running on 6.7.4-arch1-1. It is possible the bug has been patched for the newer Arch kernel. I have a bluetooth mouse that runs with no problems.
Let me warn you that the mods are going to close this thread as I said Manjaro is not supported here.

seth · 2024-02-16 09:03:38

Ahemm…

you on that bug wrote:

I'm affected too on Linux 6.7.0-0-MANJARO x86_64, bluez 5.71 (which is the most up-to-date in the repos)

That aside, the OP of the linked bug suggests that

my BT remote properly working with the bluez 5.48 without any issue

and they're facing the problem w/ 5.66 that was outdated by june last year.
Nevertheless, did you try to downgrade kernel or bluez?

WorMzy · 2024-02-16 09:12:19

Manjaro is not supported here, this was made clear during the registration process (your account probably predates the 'agree to these rules' prompt, however they still apply). Please seek support from the Manjaro support channels.

https://bbs.archlinux.org/misc.php?action=rules

Closing, for deletion.

Last edited by WorMzy (2024-02-16 12:18:35)

Arch Linux

#1 2024-02-15 08:32:43

Bluetooth mouse in disconnection loops

#2 2024-02-16 06:44:40

Re: Bluetooth mouse in disconnection loops

#3 2024-02-16 08:19:18

Re: Bluetooth mouse in disconnection loops

#4 2024-02-16 08:20:02

Re: Bluetooth mouse in disconnection loops

#5 2024-02-16 08:22:41

Re: Bluetooth mouse in disconnection loops

#6 2024-02-16 08:23:35

Re: Bluetooth mouse in disconnection loops

#7 2024-02-16 08:29:30

Re: Bluetooth mouse in disconnection loops

#8 2024-02-16 08:53:54

Re: Bluetooth mouse in disconnection loops

#9 2024-02-16 09:02:08

Re: Bluetooth mouse in disconnection loops

#10 2024-02-16 09:03:38

Re: Bluetooth mouse in disconnection loops

#11 2024-02-16 09:12:19

Re: Bluetooth mouse in disconnection loops

Board footer