FS#71157 - [alsa-ucm-conf] [pipewire] 1.2.5 breaks front headphone output on pipewire-pulse (Matisse)

Attached to Project: Arch Linux
Opened by Alexander Mezin (Sanya_M) - Monday, 07 June 2021, 12:13 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 10 June 2021, 23:12 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

After upgrade to 1.2.5, front headphone output isn't working.
In GNOME Settings, when I select front headphone output and click "Test", it shows a dialog with text "Click a speaker to test", but there are no buttons to click.

`systemctl --user status pipewire` shows this:

Jun 06 04:40:30 trx40 systemd[2732]: Started Multimedia Service.
Jun 06 04:40:41 trx40 pipewire[44766]: '_ucm0005.hw:ALC1220VBDT,2': playback open failed: No such device
Jun 06 04:40:41 trx40 pipewire[44766]: adapter 0x559741478670: can't get format: No such device
Jun 06 04:40:41 trx40 pipewire[44766]: usage: node.name=<string>
Jun 06 04:40:41 trx40 pipewire[44766]: '_ucm0005.hw:ALC1220VBDT,1': playback open failed: No such device
Jun 06 04:40:41 trx40 pipewire[44766]: adapter 0x559741530560: can't get format: No such device
Jun 06 04:40:41 trx40 pipewire[44766]: usage: node.name=<string>

Downgrading alsa-ucm-conf to 1.2.4 fixes the issue

git bisect points to 1e6297b as first bad commit in alsa-ucm-conf

Upstream bug reports:
- https://github.com/alsa-project/alsa-ucm-conf/issues/98
- https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1269

Steps to reproduce:

Use pipewire-pulse as pulseaudio server

Upgrade alsa-ucm-conf to 1.2.5
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Thursday, 10 June 2021, 23:12 GMT
Reason for closing:  Fixed
Additional comments about closing:  pipewire 1:0.3.30-2
Comment by David Runge (dvzrv) - Tuesday, 08 June 2021, 07:32 GMT
@Sanya_M: Thanks for the report!

It seems there is also an upstream report [1] in regards to this commit [2] not being applied on top of 1.2.5.
Did you try whether that fixes your issue?


[1] https://github.com/alsa-project/alsa-lib/issues/148
[2] https://github.com/alsa-project/alsa-ucm-conf/commit/3f34021beffba4e39f064a14c5faceeaa224b766
Comment by David Runge (dvzrv) - Tuesday, 08 June 2021, 07:40 GMT
Hm, according to your bug report towards pipewire you seem to have tried even commits after that.
I guess this one is for upstream ALSA to figure out then. Thanks for the investigation!
Comment by Thomas Schneider (BlackLotus) - Thursday, 10 June 2021, 12:34 GMT
possible upstream fix https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1286
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/23a0f29d48781118a24f3752c94e81e470f89bb7
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/283e13629c0e98669a1b39597f233eaa0f61f552

works for me (tm)
Comment by Alexander Mezin (Sanya_M) - Thursday, 10 June 2021, 21:50 GMT
Fixed in current pipewire git master branch.
Fix in Fedora: https://src.fedoraproject.org/rpms/pipewire/c/5374ca891c98d31c5c5355230c9616c607a0078d?branch=rawhide (4 patches)

Loading...