Thank you for the report. From the wireplumber status, the Bluetooth
device has been configured as both the default sink and the default
source:
Default Configured Devices:
0. Audio/Sink bluez_output.28:11:A5:AF:C3:AC
1. Audio/Source bluez_input.28:11:A5:AF:C3:AC
Keeping a Bluetooth input active forces the device toward the HFP/HSP
headset profile, which may explain the repeated a2dp-source profile
connect failed ... Device or resource busy and the SCO traffic in the
journal.
Could you try clearing the stored state and retesting?
systemctl --user stop wireplumber pipewire pipewire-pulse
rm -rf ~/.local/state/wireplumber
systemctl --user start wireplumber pipewire pipewire-pulse
Then reconnect the headphones and, while audio is playing, attach the
output of:
wpctl status
looking to confirm the device sits in A2DP with no active source node.
** Changed in: pipewire (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2154643
Title:
Bluetooth audio "scratching"/crackling with A2DP on Kubuntu 26.04
(works on KDE Neon)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2154643/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
