FS#79044 - [pipewire] loss of audio when using Bluetooth devices

Attached to Project: Arch Linux
Opened by Sergio Conde (skgsergio) - Monday, 10 July 2023, 16:27 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 12 July 2023, 07:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
David Runge (dvzrv)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 8
Private No

Details

Description:
When using remote drivers in Pipewire like Bluetooth devices loss of audio is suffered when multiple audio streams are played.

Upstream is patched, opening this bug in case that is possible to apply the patch to Arch package.

Additional info:
* .72 and .73 are affected, .71 was the last working one.
* Upstream bug report: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3316
* Upstream patch: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/4456f2efd16d6190989a903f70f4419c2ca4c819

Steps to reproduce:
Use a Bluetooth headset
Play audio from YouTube (for example)
Receive a notification or play an audio message in telegram (doesn't trigger 100% of the time but fairly easy)
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 12 July 2023, 07:18 GMT
Reason for closing:  Fixed
Additional comments about closing:  pipewire 1:0.3.73-2
Comment by Oleksandr Natalenko (post-factum) - Monday, 10 July 2023, 16:38 GMT
I also experience this issue with .72 and .73.

Please note however that one patch is not enough. The whole submission of today's patches (namely: f459320968, a966d4806b, 3e0050d1cd, 098ac51272, 4456f2efd1) must be pulled in. Or better just use the latest HEAD of master, it is tested by multiple people as of now, and it is confirmed to have the issue fixed.
Comment by Sergio Conde (skgsergio) - Tuesday, 11 July 2023, 05:58 GMT
For me, cherrypicking just the 4456f2efd16d6190989a903f70f4419c2ca4c819 commit over .73 works for the audio loss. Probably the Input/Output errors thing persists but the important part is fixed. I guess is better to cherry-pick the minimum possible.

Edit: As confirmed by Wim, only this commit is required to fix it over .73
Comment by Oleksandr Natalenko (post-factum) - Tuesday, 11 July 2023, 17:08 GMT
OK, thanks for checking that.

heftig, dvzrv, please apply 4456f2efd1 only. I'm not sure when the next release will be, and at the same time last two versions are unusable for those who use BT headsets.

Loading...