Bluetooth periodically loses connectivity to already-connected devices and stops discovery 24.03.3 LTS

Ubuntu Version:
Ubuntu 24.04.3 LTS
Lenovo ThinkPad T14 Gen 5
Intel® Core™ Ultra 5 125H × 18
Linux 6.14.0-29-generic

fully patched, standard desktop environment

Problem Description:
After a sleep, periodically (not consistently) my laptop will no longer reconnect to my bluetooth mouse. Restarting fixes it. Logging out does not. I can’t see a pattern in what precedes the loss of reconnectivity.
Also, once in the state of not connecting, it does not let me connect a new device (ie. if I switch the mouse to one of its alternative channels), as the device is not discovered.

Relevant System Information:
Logitech MX Vertical
bluetoothctl info

Device F0:B7:EA:51:81:F4 (random)
	Name: MX Vertical
	Alias: MX Vertical
	Appearance: 0x03c2 (962)
	Icon: input-mouse
	Paired: yes
	Bonded: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	WakeAllowed: yes
	LegacyPairing: no
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
	UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00010000-0000-1000-8000-011f2000046d)
	Modalias: usb:v046DpB020d0009
	Battery Percentage: 0x64 (100)
[MX Vertical]#

hciconfig

$ hciconfig
hci0:	Type: Primary  Bus: USB
	BD Address: 5C:B4:7E:D2:84:B6  ACL MTU: 1021:4  SCO MTU: 96:6
	UP RUNNING PSCAN 
	RX bytes:485683 acl:26749 sco:0 events:268 errors:0
	TX bytes:9195 acl:67 sco:0 commands:156 errors:0

inxi

 $ inxi --bluetooth
Bluetooth:
  Device-1: Intel driver: btusb type: USB
  Report: hciconfig ID: hci0 state: up address: 5C:B4:7E:D2:84:B6 bt-v: 5.4

What I’ve Tried:
I’m not technical enough to try anything fancy. I’m reporting here in case it helps isolate cause for maintainers.
I’ve not reported the issue for months because I had hoped the issue would be found and patched over time, given multiple other reports. Other threads with similar reported behaviour:

They have not found answers either.

This topic was automatically closed after 30 days. New replies are no longer allowed.