Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#67626 - [pipewire] 0.3.8 udev rules / alsa profiles potentially break pulseaudio 13 device detection

Attached to Project: Arch Linux
Opened by David Roth (V1del) - Tuesday, 18 August 2020, 10:46 GMT
Last edited by freswa (frederik) - Tuesday, 18 August 2020, 22:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Jan de Groot (JGC)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No


Description: After upgrading to pipewire 0.3.8 my Astro A50 headset was unable to be initalized by pulseaudio. A quick comparison showed that pipewire is now intending to ship the pulse profile configurations as well as relevant udev rules redirecting to them. With the current stable release states having pulseaudio and pipewire installed can lead to issues for the former, since pipewire ships files that are intended for newer versions of pulse (FWIW for this particular case likely at least would be needed, but from eyeballing a lot of changes in this logic have happened between pulse versions and many other devices might be affected)

This is likely a transient problem that is going to be fixed "automatically" once the newer pulse version ships, but right now this can potentially break users setups if they remain with the stable repositories.

Additional info:
* package version(s) 0.3.8-1 0.3.8-2
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce: Have a device that has newer profile information in the pipewire 0.38 release than is present in the current stable release of pulseaudio, pulseaudio won't proper initialize said device.
This task depends upon

2020-10-19: A task closure has been requested. Reason for request: Should be fixed with the combination of the profile files in alsa-card-profiles and the updated pulse snapshot