Bluetooth fails to connect "br-connection-profile-unavailable"

Bug #1966436 reported by EdwardO
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Undecided
Unassigned
pipewire (Ubuntu)
Invalid
Undecided
Unassigned
pulseaudio (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

How to reproduce:

> bluetoothctl scan on
Discovery started
...
> bluetoothctl connect 94:DB:56:8E:0B:96
Attempting to connect to 94:DB:56:8E:0B:96
Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable

> systemctl status bluetooth
bluetooth.service - Bluetooth service
     Loaded: loaded
...
mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available

Notes:
kernel-5.15, bluez-5.64
Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
Dell Precision 3560
Unfortunately I did not test before upgrade to 22.04.
Tried installing pipewire-pulse, blueman, but this is lower-level.
There are reports of similar errors popping up in Arch and Manjaro recently:
https://bbs.archlinux.org/viewtopic.php?id=270465
https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Mar 25 12:56:34 2022
InstallationDate: Installed on 2022-03-04 (21 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Precision 3560
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago)
dmi.bios.date: 09/13/2021
dmi.bios.release: 1.12
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.2
dmi.board.name: 095HH7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22:
dmi.product.family: Precision
dmi.product.name: Precision 3560
dmi.product.sku: 0A22
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0: Type: Primary Bus: USB
  BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6
  UP RUNNING PSCAN
  RX bytes:24189 acl:41 sco:0 events:519 errors:0
  TX bytes:8252 acl:33 sco:0 commands:239 errors:0
modified.conffile..etc.cron.daily.apport: [deleted]

Revision history for this message
EdwardO (edwardooo) wrote :
Revision history for this message
EdwardO (edwardooo) wrote :

I found recent bugs but:
* this is not the same adapter as #1960448
* not same adapter as #1960377 and I'm running 5.15.0-23-generic which is supposed to have the fix mentioned.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Profile selection is probably related to the sound server in use, so this should be assigned there too (pulseaudio or pipewire).

tags: added: a2dp
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

What is the model of the audio device?

Revision history for this message
EdwardO (edwardooo) wrote (last edit ):

Indeed audio is also broken since the update (no audio device is found), I didn't think bluetooth audio was related to the wired one, but if so this bug is misrouted.

lspci -nnk | grep -A2 Audio
0000:00:1f.3 Audio device [0403]: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
        Subsystem: Dell Tiger Lake-LP Smart Sound Technology Audio Controller [1028:0a22]
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

aplay --list-devices
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC3204 Analog [ALC3204 Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
... up to HDMI 11

sudo dmesg | grep snd
[ 293.314241] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380
[ 293.314682] snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002)
[ 293.314933] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[ 293.480757] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 293.480761] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 293.480762] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 293.480764] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 293.480769] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 293.480770] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19
[ 293.480772] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a
[ 293.480773] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12

journalctl -b --user -u pipewire -u pipewire-pulse -u pipewire-media-session
mars 28 16:33:39 ncelrnd2375 systemd[2780]: Started PipeWire Multimedia Service.
mars 28 16:33:39 ncelrnd2375 systemd[2780]: Started PipeWire Media Session Manager.
mars 28 16:33:39 ncelrnd2375 systemd[2780]: Started PipeWire PulseAudio.
mars 28 16:33:39 ncelrnd2375 pipewire-pulse[2803]: 536870912
mars 28 16:33:39 ncelrnd2375 pipewire-media-session[2789]: ms.core: error id:32 seq:229 res:-38 (Function not implemented): no interface PipeWire:Interface:Client

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

What is the model of the Bluetooth device/headphones/speaker?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Oh this is KDE too, so I wonder if that chooses PipeWire instead of PulseAudio. If so then please try a regular Ubuntu 22.04 live session (GNOME).

Revision history for this message
EdwardO (edwardooo) wrote :

Thanks for the support.

Indeed pipewire is part of the issue. Although installing kubuntu-desktop does not force pipewire (according to https://packages.ubuntu.com/jammy/kubuntu-desktop ), I may have enabled it wrongly while getting Wayland screensharing to work with the following:

sudo apt install xdg-desktop-portal-gnome gnome-remote-desktop # installs pipewire

systemctl --user enable pipewire-media-session
systemctl --user start pipewire-media-session
systemctl --user restart xdg-desktop-portal-gnome

This must have been what caused audio to break
(aside - I'd be happy to know the supported steps for xdg-portal sharing when upgrading to 22.04)

Thanks to your pointer I managed to fix it:
* recover the (wired) audio by installing wireplumber: this fixed half-setup pipewire situation.
* fix bluetooth by installing libspa-0.2-bluetooth (and restart bluetooth & wireplumber)
(see https://<email address hidden>/msg1826833.html)
So, closing this, and if it is considered an unsupported solution, sorry for taking your time!

Changed in bluez (Ubuntu):
status: New → Invalid
Changed in pipewire (Ubuntu):
status: New → Invalid
Changed in pulseaudio (Ubuntu):
status: New → Invalid
Revision history for this message
antgel (antgel) wrote :

Thanks for this - I couldn't pair a simple Bluetooth speaker on 22.04 upgraded from 22.04. I didn't even know that pipewire was a thing nor that it crept in. Now it's working well, hopefully my JACK configuration will continue to work well as well...

Revision history for this message
Aleksandr Panzin (jalexoid) wrote :

Installing libspa-0.2-bluetooth helped me

As well sa manually pairing the Bluetooth headphones.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.