Can't establish bluetooth connection

Hello :slight_smile:
I realised that I am unable to create a bluetooth connection to an arbitrary device with the current KDE release version manjaro-kde-23.1.1 (minimal and normal version). This is true for a fresh installation, but also in live-usb-mode. If you try it via GUI it takes some time and then says that the setup with the device fails. “bluetoothctl” gives me an authentication timeout at some point.
I tried Manjaro GNOME or Fedora KDE and there it is just working fine. On manjaro-kde-23.0.4 it is also working, but tested on a different device.
Any known reported issues regarding this?

Best regards!

Hi @wiesel,

Sounds like a driver is missing. But we can’t check without more info, so we need more information. To that end, please see:

Please also note and heed: Forum Rules - Manjaro

Hope you manage!


:bangbang: Tip: :bangbang:

To provide terminal output, copy the text you wish to share, and paste it here, surrounded by three (3) backticks, a.k.a grave accents. Like this:

```
pasted text
```

Or three (3) tilde signs, like this:

~~~
pasted text
~~~

This will just cause it to be rendered like this:

Portaest sed
elementum
cursus nisl nisi
hendrerit ac quis
sit
adipiscing
tortor sit leo commodo.

Instead of like this:

Portaest sed elementum cursus nisl nisi hendrerit ac quis sit adipiscing tortor sit leo commodo.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby improving legibility and making it much easier for those trying to be of assistance.


:bangbang::bangbang: Additionally

If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

Please edit your post accordingly.

Not sure about bluetoothctl on KDE plasma. Try:

LC_ALL=C sudo systemctl status bluetooth.service
LC_ALL=C sudo journalctl -u bluetooth.service -xe --no-pager

But there is also a Gnome tag in the title of the post so… :person_shrugging:

That was just an example, it’s purely coincidence that it fits in with the title.

:wink:

Hello,
happy to provide any missing information.

sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sun 2023-12-31 15:20:35 CET; 8min ago
       Docs: man:bluetoothd(8)
   Main PID: 609 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 37537)
     Memory: 2.8M
        CPU: 17ms
     CGroup: /system.slice/bluetooth.service
             └─609 /usr/lib/bluetooth/bluetoothd

Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/sbc
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/sbc
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/sbc_x>
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/sbc>
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/sbc_x>
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/sbc>
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/sbc_x>
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/sbc>
Dez 31 15:20:59 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:59 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)

and

sudo journalctl -u bluetooth.service -xe --no-pager
Dez 31 15:20:35 w-sys systemd[1]: Starting Bluetooth service...
░░ Subject: A start job for unit bluetooth.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit bluetooth.service has begun execution.
░░ 
░░ The job identifier is 137.
Dez 31 15:20:35 w-sys bluetoothd[609]: Bluetooth daemon 5.71
Dez 31 15:20:35 w-sys bluetoothd[609]: Starting SDP server
Dez 31 15:20:35 w-sys bluetoothd[609]: src/plugin.c:plugin_init() System does not support csip plugin
Dez 31 15:20:35 w-sys bluetoothd[609]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Dez 31 15:20:35 w-sys bluetoothd[609]: src/plugin.c:plugin_init() System does not support micp plugin
Dez 31 15:20:35 w-sys bluetoothd[609]: src/plugin.c:plugin_init() System does not support vcp plugin
Dez 31 15:20:35 w-sys bluetoothd[609]: src/plugin.c:plugin_init() System does not support mcp plugin
Dez 31 15:20:35 w-sys bluetoothd[609]: src/plugin.c:plugin_init() System does not support bass plugin
Dez 31 15:20:35 w-sys bluetoothd[609]: src/plugin.c:plugin_init() System does not support bap plugin
Dez 31 15:20:35 w-sys bluetoothd[609]: Bluetooth management interface 1.22 initialized
Dez 31 15:20:35 w-sys bluetoothd[609]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Dez 31 15:20:35 w-sys bluetoothd[609]: Battery Provider Manager created
Dez 31 15:20:35 w-sys systemd[1]: Started Bluetooth service.
░░ Subject: A start job for unit bluetooth.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░ 
░░ A start job for unit bluetooth.service has finished successfully.
░░ 
░░ The job identifier is 137.
Dez 31 15:20:35 w-sys bluetoothd[609]: Failed to clear UUIDs: Failed (0x03)
Dez 31 15:20:35 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:35 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:35 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:35 w-sys bluetoothd[609]: Failed to set mode: Failed (0x03)
Dez 31 15:20:35 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:35 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:35 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:58 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:58 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:58 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:58 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:58 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:58 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:58 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:59 w-sys bluetoothd[609]: Failed to set mode: Failed (0x03)
Dez 31 15:20:59 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:59 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/ldac_hq
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/ldac_sq
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/ldac_mq
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/aptx_hd
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/aptx_hd
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/aptx
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/aptx
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/sbc
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/sbc
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Dez 31 15:20:59 w-sys bluetoothd[609]: Endpoint registered: sender=:1.46 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Dez 31 15:20:59 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)
Dez 31 15:20:59 w-sys bluetoothd[609]: Failed to add UUID: Failed (0x03)

Is “Failed to add UUID” of interest? How would I add missing drivers or how can I check if some are missing?

Best regards!

I suspect, note, I’m not sure, but suspect, this might be driver-related, yes.
Or not, according to [SOLVED] bluetoothd Failed to add UUID: Failed (0x03) / Newbie Corner / Arch Linux Forums :man_shrugging:

Please provide the output of, as requested in the second reply in the thread:

inxi --full --admin --filter --width

Please also provide the output of:

rfkill list

I see similar things in my log on my KDE plasma setup, but I never use bluetooth so I just ignore them.

I will follow with interest and see if the commands in the post above brings similar feedback on your setup as on mine.
I DO have an old bluetooth speaker I could try with to compare with you when it comes to that.

I also found this to add to the link above. Maybe you can find some useful info in that thread.

I think rfkill list looks fine.

0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

inxi --full --admin --filter --width output:

System:
  Kernel: 6.5.13-7-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.5-x86_64
    root=UUID=61adf7aa-bc4b-43dd-801b-1058364a9032 rw quiet splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.11 wm: kwin_x11 vt: 2
    dm: SDDM Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: TUF GAMING B650-PLUS WIFI v: Rev 1.xx
    serial: <superuser required> UEFI: American Megatrends v: 1811
    date: 10/07/2023
CPU:
  Info: model: AMD Ryzen 7 7700 bits: 64 type: MT MCP arch: Zen 4 gen: 5
    level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
    model-id: 0x61 (97) stepping: 2 microcode: 0xA601206
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 8 MiB desc: 8x1024 KiB
    L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 400 min/max: 400/5389 scaling: driver: amd-pstate-epp
    governor: powersave cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400
    8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400 15: 400 16: 400
    bogomips: 121422
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Raphael vendor: ASUSTeK driver: amdgpu v: kernel arch: RDNA-2
    code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1 empty: DP-1
    bus-ID: 0b:00.0 chip-ID: 1002:164e class-ID: 0300 temp: 32.0 C
  Display: x11 server: X.Org v: 21.1.10 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93") monitors: <missing: xrandr>
  Monitor-1: HDMI-A-1 model: Asus VS248 serial: <filter> built: 2019
    res: 1920x1080 dpi: 92 gamma: 1.2 size: 531x299mm (20.91x11.77")
    diag: 609mm (24") ratio: 16:9 modes: max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast surfaceless: drv: radeonsi x11: drv: radeonsi
    inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.1.9-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics
    (raphael_mendocino LLVM 16.0.6 DRM 3.54 6.5.13-7-MANJARO)
    device-ID: 1002:164e memory: 500 MiB unified: no
  API: Vulkan v: 1.3.274 layers: N/A device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RAPHAEL_MENDOCINO) driver: mesa radv
    v: 23.1.9-manjaro1.1 device-ID: 1002:164e surfaces: xcb,xlib
Audio:
  Device-1: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0b:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-2: AMD Family 17h/19h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0b:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.5.13-7-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.0.0 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 16.1 status: active with: pulseaudio-alsa
    type: plugin tools: pacat,pactl
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 07:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Realtek RTL8852BE PCIe 802.11ax Wireless Network
    vendor: AzureWave driver: rtw89_8852be v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: d000 bus-ID: 08:00.0 chip-ID: 10ec:b852 class-ID: 0280
  IF: wlp8s0 state: up mac: <filter>
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
    rev: 1.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-5:2 chip-ID: 13d3:3571
    class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
    lmp-v: 12 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
  Local Storage: total: 931.51 GiB used: 133.54 GiB (14.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Corsair model: MP600 PRO XT
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: EIFM31.6 temp: 20.9 C
    scheme: GPT
Partition:
  ID-1: / raw-size: 931.22 GiB size: 915.53 GiB (98.32%)
    used: 133.54 GiB (14.6%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 296 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A gpu: amdgpu temp: 33.0 C
  Fan Speeds (rpm): N/A
Info:
  Processes: 341 Uptime: 4m wakeups: 0 Memory: total: 32 GiB note: est.
  available: 30.57 GiB used: 2.21 GiB (7.2%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
  Packages: pm: pacman pkgs: 1169 libs: 330 tools: pamac Shell: Zsh v: 5.9
  default: Bash v: 5.2.21 running-in: konsole inxi: 3.3.31

I tried to follow up on the links, but didn’t came up with something useful. I updated the kernel from 65 to 67.

Happy new year
everyone :slight_smile:

Nothing the matter that I can see, so let’s see if someone else does.


Technically, every day is the start of a new year, so it’s not really special. Happy new calendar year, though!

:grin:

The mention of “authentication timeout” has me wondering if the problem might be related to the recent change to BlueZ to bring it in line with security standards, as discussed in another thread. The solution is in the linked post:

I could try downgrade BlueZ. Which version would you recommend?
Any other ideas how to check for missing drivers?

From the inxi output, it doesn’t seem to be missing drivers.

And according to IMC Networks Bluetooth Radio

The device is supported by kernel versions 2.6.0 and newer according to the LKDDb

However, don’t quote me on this, but they seem to only list to kernel 6.3. So another possibility would be to try an older kernel. For example, 6.1, which is an LTS version, and inn fact the kernel I use.

To install it:

sudo mhwd-kernel --install linux61

Then reboot, select it in grub, and test. If it works, remove the current, non-working one:

sudo mhwd-kernel --remove linux65

In fact, removing it is a good idea since it’s EOL anyway: Linux kernel version history - Wikipedia

See:

Switching the Kernel to 61 does actually fix the 0x03 errors, but unfortunately the issue remains.