Regression in pipewire-pulse 0.3.39 fails to switch bluetooth A2DP profile
- PipeWire version (
pipewire --version
): 0.3.39 - Distribution and distribution version (
PRETTY_NAME
from/etc/os-release
): Ubuntu 21.10 - Desktop Environment: KDE (Kubuntu)
- Kernel version (
uname -r
): 5.13.0-20-generic - BlueZ version (
bluetoothctl --version
): 5.60 -
lsusb
:
Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 046d:085c Logitech, Inc. C922 Pro Stream Webcam
Bus 001 Device 003: ID 046d:c52e Logitech, Inc. MK260 Wireless Combo Receiver
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter
Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- Bluetooth devices:
Device 00:00:AB:CD:1F:E6 VerveBuds 400
Description of Problem:
After updating to pipewire and pipewire-pulse: 0.3.39 I can not switch bluetooth A2DP profile via KDE volume control, after switching headset doesn't produce any sound and any application cannot play sound anymore even with default audio device.
How Reproducible:
Open KDE volume control in the task bar or pavucontrol in the Configuration tab and change profile to another codec (AAC -> SBC).
Actual Results:
BT headset sound disappears.
Expected Results:
BT headset start working with a new profile.
Additional Info (as attachments):
systemctl --user status pipewire-pulse.socket
:
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2021-11-03 22:56:50 EET; 9s ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 34720 (pipewire-pulse)
Tasks: 2 (limit: 18967)
Memory: 4.5M
CPU: 79ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─34720 /usr/bin/pipewire-pulse
Nov 03 22:56:55 stan-PC pipewire-pulse[34720]: pw.node: 0x55d388c69380: can't add port 0x55d388ba3fc0: -22, Invalid argument
Nov 03 22:56:55 stan-PC pipewire-pulse[34720]: pw.node: 0x55d388c69380: can't add port 0x55d388ba3fc0: -22, Invalid argument
Nov 03 22:56:55 stan-PC pipewire-pulse[34720]: pw.node: 0x55d388b9b120: output port 0 unknown
Nov 03 22:56:55 stan-PC pipewire-pulse[34720]: pw.node: 0x55d388b9b120: output port 1 unknown
Nov 03 22:56:55 stan-PC pipewire-pulse[34720]: pw.node: 0x55d388b9b120: can't add port 0x55d388ba3fc0: -22, Invalid argument
Nov 03 22:56:55 stan-PC pipewire-pulse[34720]: pw.node: 0x55d388b9b120: can't add port 0x55d388ba3fc0: -22, Invalid argument
Nov 03 22:56:55 stan-PC pipewire-pulse[34720]: pw.node: 0x55d388c69380: output port 0 unknown
Nov 03 22:56:55 stan-PC pipewire-pulse[34720]: pw.node: 0x55d388c69380: output port 1 unknown
Nov 03 22:56:55 stan-PC pipewire-pulse[34720]: pw.node: 0x55d388c69380: can't add port 0x55d388ba3fc0: -22, Invalid argument
Nov 03 22:56:55 stan-PC pipewire-pulse[34720]: pw.node: 0x55d388c69380: can't add port 0x55d388ba3fc0: -22, Invalid argument