Can't connect new bluetooth device

Hello helpful EndeavourOS folks.

I generally use a bluetooth mouse (specifically, a Logitech ergo m575 trackball). I’ve been using EndeavourOS for years and years. A couple of months shy of 4 years, to be exact:

[jason@xps139310 ~]$ stat / | grep Birth
 Birth: 2020-12-07 16:15:49.000000000 -0500

In any case, my bluetooth mouse doesn’t connect this morning (it was working fine yesterday). This is randomly happened once or twice before, and I usually just have bluetooth “forget” the device, and then reconnect. A minor annoyance every couple of years, which doesn’t take longer than a minute to fix.

But today, it seems like the “add a new device” button is gone.

At least, I seem to recall seeing a button here previously to add a new device.

Here’s some additional info about my system, in case it helps:

[jason@xps139310 ~]$ inxi
CPU: quad core 11th Gen Intel Core i7-1165G7 (-MT MCP-)
speed/min/max: 1279/400/4700 MHz Kernel: 6.11.4-arch1-1 x86_64 Up: 9m
Mem: 3.96/7.49 GiB (52.9%) Storage: 238.47 GiB (74.8% used) Procs: 269
Shell: Bash inxi: 3.3.36

 [jason@xps139310 ~]$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sat 2024-10-19 10:11:06 EDT; 10min ago
 Invocation: 875f940583ba4703aec9d1031c41955a
       Docs: man:bluetoothd(8)
   Main PID: 5143 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 9027)
     Memory: 812K (peak: 1.5M)
        CPU: 40ms
     CGroup: /system.slice/bluetooth.service
             └─5143 /usr/lib/bluetooth/bluetoothd

Oct 19 10:11:06 xps139310 bluetoothd[5143]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSourc>
Oct 19 10:11:06 xps139310 bluetoothd[5143]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/>
Oct 19 10:11:06 xps139310 bluetoothd[5143]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSourc>
Oct 19 10:11:06 xps139310 bluetoothd[5143]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/>
Oct 19 10:11:06 xps139310 bluetoothd[5143]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSourc>
Oct 19 10:11:06 xps139310 bluetoothd[5143]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/>
Oct 19 10:11:06 xps139310 bluetoothd[5143]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSourc>
Oct 19 10:11:06 xps139310 bluetoothd[5143]: Failed to set mode: Busy (0x0a)
Oct 19 10:11:21 xps139310 bluetoothd[5143]: Failed to set mode: Failed (0x03)
Oct 19 10:11:22 xps139310 bluetoothd[5143]: Failed to set mode: Busy (0x0a)
[jason@xps139310 ~]$ pacman -Qs blue
local/bluez 5.78-1
    Daemons for the bluetooth protocol stack
local/bluez-libs 5.78-1
    Deprecated libraries for the bluetooth protocol stack
local/gnome-bluetooth-3.0 47.1-1
    GNOME Bluetooth Subsystem
local/hidapi 0.14.0-3
    Simple library for communicating with USB and Bluetooth HID devices
local/libldac 2.0.2.3-2
    LDAC Bluetooth encoder library
local/pulseaudio-bluetooth 17.0-3
    Bluetooth support for PulseAudio
local/sbc 2.0-2
    Bluetooth Subband Codec (SBC) library

All that said, is there something obvious that I’m missing? Is this an issue with Gnome? I updated gnome-shell this morning (to 1:47.1-1). I generally update once every day or two. Should I just wait for the gnome folks to fix the bug? Or is there something I can do to fix bluetooth on my own?

Thanks in advance for any help!

  • Jason

It’s a bug in kernel 6.11.4. Downgrading to 6.11.3 fixes it for now.

https://bugzilla.kernel.org/show_bug.cgi?id=219385

2 Likes

great, thank you for the quick explanation! (and I’m glad to hear that it wasn’t something that I screwed up with my system).

upon seeing your response, I rebooted into the LTS kernel (6.6.57-1-lts), and I was able to reconnect my mouse without issue. It seems like it’s either using the LTS kernel until it’s fixed, or downgrading back to 6.11.3 for the time being.

Thanks again!

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.