FS#71567 - [pipewire-pulse] MSBC codec broken

Attached to Project: Arch Linux
Opened by Jürgen Richtsfeld (juri8) - Wednesday, 21 July 2021, 06:59 GMT
Last edited by David Runge (dvzrv) - Tuesday, 08 February 2022, 17:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Christian Hesse (eworm)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
MSBC codec seems to be broken since the latest upgrade to 1:0.3.32-1


Additional info:
* 1:0.3.32-1

Steps to reproduce:
I configured the `bluez-monitor.conf` quite a while ago and everything worked fine until I upgraded today to the version mentioned above. Other bluetooth codecs seem to work, when switching to msbc I can't hear anything and I'm told the I sound like 'chopped' - so the mic produces something but not understandable.
This task depends upon

Closed by  David Runge (dvzrv)
Tuesday, 08 February 2022, 17:53 GMT
Reason for closing:  No response
Additional comments about closing:  mSBC codec appears to work (currently).
Comment by Jürgen Richtsfeld (juri8) - Wednesday, 21 July 2021, 08:43 GMT
It appears I blamed the wrong library. I downgraded to the previous one (0.3.31) but I'm still having the same problems. Maybe it's the kernel 5.13.4 that also came in today (at least I have no other ideas left)
Comment by Jürgen Richtsfeld (juri8) - Wednesday, 21 July 2021, 10:14 GMT
I need to apologize here for the missing summary - I missed the input field as this was the first issue I reported...
Comment by maor (dah1) - Monday, 26 July 2021, 05:38 GMT
I'm experiencing the same issue, the issue is related to kernel 5.13 downgrade to kernel 5.12 and mSBC codec is working normally
Comment by maor (dah1) - Monday, 26 July 2021, 06:47 GMT
I'm experiencing the same issue, the issue is related to kernel 5.13 downgrade to kernel 5.12 and mSBC codec is working normally
Comment by AK (Andreaskem) - Monday, 26 July 2021, 07:10 GMT
Comment by AK (Andreaskem) - Monday, 26 July 2021, 07:11 GMT
An upstream issue suggests that Linux kernel versions 5.13.3+ break the mSBC codec:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1366
A possible fix is linked, as well:
b86543908684cc6cd9afaf4de10fac7af1a49665.camel@iki.fi/"> https://patchwork.kernel.org/project/bluetooth/patch/b86543908684cc6cd9afaf4de10fac7af1a49665.camel@iki.fi/
edit: This link gets mangled horribly, for some reason. It is linked here, as well:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1366#note_1002870
Comment by Sergiusz Urbaniak (sur) - Wednesday, 04 August 2021, 07:04 GMT
Workaround for me:
The last known working kernel version is 5.13.1.

Manually downgrading to https://archive.archlinux.org/packages/l/linux/linux-5.13.1.arch1-1-x86_64.pkg.tar.zst and https://archive.archlinux.org/packages/l/linux-headers/linux-headers-5.13.1.arch1-1-x86_64.pkg.tar.zst fixes the issue.

After downgrade pinning linux/linux-headers in /etc/pacman.conf keeps it from upgrading:

$ cat /etc/pacman.conf
...
# linux: until https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1366#note_1000362 is resolved
IgnorePkg = linux linux-headers
...

Not an ideal solution but buys some time until upstream linux fixes the issue.
Comment by Jan Alexander Steffens (heftig) - Friday, 27 August 2021, 15:25 GMT
I just got a report that it's still broken. Has the patch added back in 5.13.8.arch1-1 helped anyone?

Loading...