Recent kernel update broke Logitech G603 mouse over bluetooth, other bluetooth devices work fine

Support and Help
,
1

Ubuntu Version:
Ubuntu Desktop 24.0.2 LTS

Desktop Environment (if applicable):
GNOME 46

Problem Description:
I’ve been using a Logitech G603 mouse over Bluetooth with this laptop running Ubuntu 24.04 for quite a while. The recent update containing these packages killed the mouse immediately (it said it was paired and connected, but no mouse movements or clicks were detected). All other Bluetooth devices work fine–only the mouse fails. I tried disconnecting, unpairing, untrusting, removing the mouse using bluetoothctl, which worked, but now I can’t re-pair the mouse. Very rarely, it will be discovered in a scan. If it does discover it, I can’t get past pairing or connecting due to it timing out (the timeout error shows up in syslog, but it is not informative).

The same mouse works fine with a different Windows 11 PC over Bluetooth. It also works fine with this Ubuntu 24.04.2 laptop when using the USB receiver. So it is just this mouse over bluetooth that doesn’t work. I do not have other bluetooth mice to test with. It could be all bluetooth mice fail, just Logitech bluetooth mice fail, or just this one specific Logitech G603 mouse fails.

Here are the packages that were upgraded and the ones that were autoremoved:

Start-Date: 2025-02-12  12:54:16
Commandline: apt upgrade
Requested-By: me (1000)
Install: linux-hwe-6.11-tools-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-extra-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-image-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-tools-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-hwe-6.11-headers-6.11.0-17:amd64 (6.11.0-17.17~24.04.2, automatic), linux-headers-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic), linux-modules-6.11.0-17-generic:amd64 (6.11.0-17.17~24.04.2, automatic)
Upgrade: linux-headers-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-tools-common:amd64 (6.8.0-52.53, 6.8.0-53.55), base-files:amd64 (13ubuntu10.1, 13ubuntu10.2), bpftrace:amd64 (0.20.2-1ubuntu4.2, 0.20.2-1ubuntu4.3), linux-image-generic-hwe-24.04:amd64 (6.8.0-52.53, 6.11.0-17.17~24.04.2+2), linux-firmware:amd64 (20240318.git3b128b60-0ubuntu2.7, 20240318.git3b128b60-0ubuntu2.9), code:amd64 (1.97.0-1738713410, 1.97.1-1739197498), microsoft-edge-stable:amd64 (132.0.2957.140-1, 133.0.3065.59-1), linux-libc-dev:amd64 (6.8.0-52.53, 6.8.0-53.55)
End-Date: 2025-02-12  12:55:35

Start-Date: 2025-02-12  15:26:04
Commandline: apt autoremove
Requested-By: me (1000)
Remove: linux-modules-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-image-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-tools-6.8.0-51:amd64 (6.8.0-51.52), linux-tools-6.8.0-51-generic:amd64 (6.8.0-51.52), linux-headers-6.8.0-51:amd64 (6.8.0-51.52), linux-modules-extra-6.8.0-51-generic:amd64 (6.8.0-51.52)
End-Date: 2025-02-12  15:26:12

System Information:
I have a StarLabs StarLite Mark V LINUX tabet.
It has an Intel N200 CPU and Intel Wifi and Bluetooth.
Here’s what the lsusb says regarding the bluetooth adapter:
“Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)”
I’m not sure hardware matters since other Bluetooth devices work just fine (an IKEA FREKVENS 10x20 bluetooth speaker that shows up as a headset and an 8BitDo SN30 Pro gamepad game controller).

What I have tried:
Completely removing the mouse from bluetoothctl, attempting to re-pair, re-connect, and re-trust using either bluetoothctl or the GNOME Settings app both fail with timeouts in the syslog.

I removed and re-installed all packages for bluez or bluetooth, but that made no difference (I didn’t expect this to help, since they were not in the update anyway. This is most likely a kernel bug.)

Any help is appreciated! Oh, I have not tried downgrading the kernel, but I am not interested in downgrading. I’d rather see the bug fixed going forward and want to help by providing logs/diagnostic results.

2

You may want to have a terminal open running sudo dmesg -w or tail -f /var/log/syslog and see if anything related shows. I tried my Logitech travel mouse over bluetooth and had issues until I replaced the batteries

3

Thanks.

I didn’t/don’t see any particular messages about the mouse movements (read somewhere I can watch the hidraw log for that). The mouse, even when bluetoothctl says it is paired and connected, simply seems like it is disconnected or missing.

I do see in syslog the attempt to pair and the subsequent timeout when trying to pair.

It might be necessary to enable debug-level logging somewhere, but I don’t know where…

And I did try a brand new battery–thanks!

Maybe it is worth the effort to buy or borrow a different brand of Bluetooth mouse to see if this affects all bluetooth mice or just Logitech or just this one mouse.

4

Hi!
I have the same problem on the same adapter
After kernel update bluetooth mouse and keyboard stopped working.
If you have any luck, let me know.

5

You’ve been super-helpful just by confirming the problem exists for more than one person!

I realized that I have a second, low-end USB-to-Bluetooth adapter somewhere. I think it is a RealTek adapter. It was bought for and works with Raspberry Pi. When I find it, I will use it to test the Logitech G603 mouse. If it works, then we know it’s related to the Intel adapter.

What mouse do you use? If it is anything other than Logitech, you have saved me the trouble of buying a different brand of Bluetooth mouse.

Also, the fact that your keyboard stopped working may mean this is HID/HCI-related, given that my speaker and gamepad still work fine.

Thanks!

6

Good news! Using my second Bluetooth adapter, my Logitech G603 mouse showed up, paired and connected right away, and the mouse functions as expected.

This means the problem is related to just the “Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)” adapter inside the tablet.

I do not know if other Bluetooth mice would work fine with the Intel adapter–they might.

The USB-to-Bluetooth adapter I am using to test shows up in lsusb as “Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)” It’s a lowly Bluetooth 4.0 adapter.

7

Have you tried doing a search on the PCI ID of that adapter? Might reveal some clues if there’s something broken in the kernel.

8

Good idea. Not yet–I will search for the ID now.
I suspect the internal Intel adapter is USB-only. It doesn’t seem to show up in the lspci output.

It does show up in the lsusb output here:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)

I will search for 8087:0aaa.

Thanks!

9

As far as my understanding goes, Bluetooth is always using the USB bus, even when internal.

1 Like
10

My Mouse is not logitech.
I don’t use Ubuntu but came across your post… I tried all the options I could find on the internet but no luck. In the meantime I found out that it happens between 6.10 and 6.11 kernel versions.

11

Ah, I think you are right. I had a PCI-express Intel Wifi+Bluetooth card in a prior desktop, and I was puzzled why it had the Bluetooth portion of the card connected to the USB bus.

12

Thanks for the extra info!
If this is not specific to Ubuntu, then we should expect to see more reports across multiple distros soon.

I will probably have to report this to the LINUX kernel ticketing system to get it fixed.

13

Is it fixed in 6.12, 6.13, or 6.14?

I wouldn’t unless you can confirm that it’s not present in the most recent version. 6.14-rc4 is available upstream.

You may, however, want to file an ubuntu-bug.

1 Like
14

I’m using 6.13.4 and it doesn’t work.
I will try 6.14-rc4 tomorrow and give you an answer

2 Likes
15

Assuming it does not, I have a really wild suggestion. First, start by going through all the release candidates for 6.11 first. Assuming they all fail, apply a binary search to the commits between 6.10 and 6.11-rc1. It will take a bit of time, I’m sure, but I’m sure you’ll find the one commit that’s the problem.

1 Like
16

The only change I noticed when using my internal Intel Bluetooth device is that the mouse movement would timeout and I would have to use the scroll wheel to get it working again, the timeout isn’t the same with the Realtek based Edimax Bluetooth device.

The only PCI Bluetooth device that I know of is the RT3290 and that never had support from the Linux kernel because Ralink didn’t help with development

1 Like
17

Do you have this specific Intel Bluetooth device, or a different model?

ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)

My suspicion is that this issue is only with this device, otherwise we’d see a lot more screaming on online forums about kernel 6.11 breaking Bluetooth keyboards and mice…

I will see if I can find a different Intel Bluetooth adapter to test. I could dual-boot my Windows 11 desktop, since that has a different Intel Bluetooth device on the motherboard…

18

Just searching through the release notes for kernel 6.11, there are no mentions of the ID 8087:0aaa, nor any mentions of “Jefferson”, nor any mentions of “Intel bluetooth”–but there are 362 hits for the word “bluetooth”.

I guess they wouldn’t hand it to us on a silver platter, haha. Looks like we’ve got a few hours of digging to do to find which kernel 6.11 RC it was introduced in and which of hundreds of changes it might be.

I’ll start digging once deshkoam confirms that the latest 6.14-rc4 also doesn’t work.

19

I am sure mine is 8087:0026 Intel Corp. AX201 Bluetooth. Might have to see if one of my other computers has the 0aaa device

1 Like
20

Yeah they usually won’t mention specific devices. Usually changes are made to larger classes of devices.