Affected by this regression as well.
Device: Sony WH-CH720N headphones (A2DP sink + HFP headset, Modalias
usb:v054Cp0EAFd0108)
OS: Pop!_OS 24.04 LTS (noble base, apt.pop-os.org/ubuntu noble)
bluez/libbluetooth3: 5.72-0ubuntu5.5
Audio stack: PipeWire 1.5.85 / WirePlumber 0.5.12
Symptoms are identical to the report: after connecting, only HSP/HFP
profiles appear on the card, no a2dp-sink. bluetoothd logs:
src/service.c:btd_service_connect() a2dp-sink profile connect failed
for <MAC>: Device or resource busy
and after restarting wireplumber/bluetoothd:
src/service.c:btd_service_connect() a2dp-sink profile connect failed
for <MAC>: Protocol not available
Sometimes also seen before the failure:
profiles/audio/avdtp.c:handle_unanswered_req() No reply to
SetConfiguration request
Additional data points from testing on this system:
1. The failure mode depends on stale daemon state, not on the package
being installed per se: a fresh pair (bluetoothctl remove + pair)
restores working A2DP, which then survives connect/disconnect cycles
until some later restart breaks it again.
2. Important for triage: removing the a2dp_source role from WirePlumber's
bluez5.roles makes it *worse* -- every connection then fails with
"Protocol not available", because in this codebase both
a2dp_sink_profile and a2dp_source_profile share the same adapter probe
that initializes the A2DP server. This suggests the noble backport of
the audio profile updates (LP: #2122382, patch
audio-upgrade-versions-to-latest-possible-to-qualify.patch) pulled in
the profile-connection-order change without the accompanying ordering
fix.
3. Working recovery sequence found so far:
bluetoothctl disconnect <MAC>
systemctl --user restart wireplumber
bluetoothctl connect <MAC>
pactl set-card-profile bluez_card.<MAC> a2dp-sink # if HFP got selected
Upstream has already fixed this exact issue in master:
https://github.com/bluez/bluez/commit/066a164a524e4983b850f5659b921cb42f84a0e0
("a2dp: connect source profile after sink", adds .after_services,
fixes https://github.com/bluez/bluez/issues/1898)
Arch Linux cherry-picked it into their 5.86-5 package in April 2026 and
it resolves the problem there.
Request: please consider backporting commit
066a164a524e4983b850f5659b921cb42f84a0e0
into the noble SRU as part of this regression.
** Bug watch added: github.com/bluez/bluez/issues #1898
https://github.com/bluez/bluez/issues/1898
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2159829
Title:
Regression in BlueZ 5.72-0ubuntu5.5 prevents A2DP connection to Amazon
Echo Dot 4 on Ubuntu 24.04.4 LTS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2159829/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
