Ubuntu 22.10 connection bluetooth headset error 'br-connection-profile-unavailable solution'

calendar 2022-10-21 · 3 min read · bluetooth Linux Ubuntu  ·
Share on: linkedin copy

The new version of Ubuntu 22.10 was released today. After the upgrade, I found that: 1. Flameshot is abnormal; 2. The AirPods Pro2 headset cannot be connected; 3. The gnome plug-in for custom ibus is not compatible (as expected).

When the Bluetooth headset cannot be connected, the symptom is Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable :

1    [bluetooth]# connect C0:95:6D:C0:A3:92
2    Attempting to connect to C0:95:6D:C0:A3:92
3    Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable

bluetooth service show： src/service.c:btd_service_connect() a2dp-sink profile connect failed for C0:95:6D:C0:A3:92: Protocol not available

 1    ➜  systemctl status bluetooth.service
 2    ● bluetooth.service - Bluetooth service
 3        Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
 4        Active: active (running) since Fri 2022-10-21 14:21:09 CST; 4min 56s ago
 5        Docs: man:bluetoothd(8)
 6    Main PID: 2973 (bluetoothd)
 7        Status: "Running"
 8        Tasks: 1 (limit: 18897)
 9        Memory: 1.6M
10            CPU: 451ms
11        CGroup: /system.slice/bluetooth.service
12                └─2973 /usr/lib/bluetooth/bluetoothd
13
14    Oct 21 14:21:09 workpc systemd[1]: Started Bluetooth service.
15    Oct 21 14:21:09 workpc bluetoothd[2973]: Bluetooth management interface 1.22 initialized
16    Oct 21 14:22:13 workpc bluetoothd[2973]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for C0:95:6D:C0:A3:92: Protocol not available
17    Oct 21 14:22:14 workpc bluetoothd[2973]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for C0:95:6D:C0:A3:92: Protocol not available
18    Oct 21 14:23:24 workpc bluetoothd[2973]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for C0:95:6D:C0:A3:92: Protocol not available
19    Oct 21 14:23:26 workpc bluetoothd[2973]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for C0:95:6D:C0:A3:92: Protocol not available
20    Oct 21 14:23:39 workpc bluetoothd[2973]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for C0:95:6D:C0:A3:92: Protocol not available
21    Oct 21 14:24:23 workpc bluetoothd[2973]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for C0:95:6D:C0:A3:92: Protocol not available
22    Oct 21 14:24:34 workpc bluetoothd[2973]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for C0:95:6D:C0:A3:92: Protocol not available
23    Oct 21 14:24:36 workpc bluetoothd[2973]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for C0:95:6D:C0:A3:92: Protocol not available

This is the daily life of linux users. After searching, it is determined that the general reason is that the audio service of the desktop version of Ubuntu 22.10 is switched from PulseAudio to PipeWire, which causes the service to be abnormal.

Solution

    1. Install dependencies
    1sudo apt install wireplumber libspa-0.2-bluetooth wireplumber-doc

Dependency package explanation

  • WirePlumber is a modular session / policy manager for PipeWire

  • libspa-0.2-bluetooth: libraries for the PipeWire multimedia server - bluetooth plugins

    1. restart wireplumber
    1   systemctl --user restart wireplumber
    1. Reconnect the AirPods earphones, see the final return to successful
     1   ➜ bluetoothctl
 2   Agent registered
 3   [bluetooth]# connect C0:95:6D:C0:A3:92
 4   Attempting to connect to C0:95:6D:C0:A3:92
 5   [CHG] Device C0:95:6D:C0:A3:92 Connected: yes
 6   [NEW] Endpoint /org/bluez/hci0/dev_C0_95_6D_C0_A3_92/sep1
 7   [NEW] Endpoint /org/bluez/hci0/dev_C0_95_6D_C0_A3_92/sep2
 8   [NEW] Endpoint /org/bluez/hci0/dev_C0_95_6D_C0_A3_92/sep3
 9   [NEW] Transport /org/bluez/hci0/dev_C0_95_6D_C0_A3_92/sep1/fd0
10   [CHG] Transport /org/bluez/hci0/dev_C0_95_6D_C0_A3_92/sep1/fd0 Delay: 0x05dc (1500)
11   Connection successful

If you have other questions, such as you don't know how to get your device's mac address, you can check out another article I wrote before

Lastmod： Monday, August 28, 2023

Copyright statement:

  • All content on this site is original, please do not reprint without authorization (because the typesetting is often disordered after reprinting, the content is uncontrollable, and cannot be continuously updated, etc.);
  • For non-profit purposes, to deduce any content of this blog, please give the relevant webpage address of this site in the form of 'source of original text' or 'reference link' (for the convenience of readers).

See Also:

Translations: