FS#73377 - [pipewire] 0.3.43 hangs after suspend

Attached to Project: Arch Linux
Opened by Jamp (jamp) - Sunday, 16 January 2022, 10:05 GMT
Last edited by David Runge (dvzrv) - Saturday, 19 February 2022, 12:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No



I am using pipewire on an AMD Ryzen 3900x based dektop PC. I am using an external USB audio device. Resuming after suspend causes the applications to hang (e.g. firefox) until the device is unplugged. Sound is restored normally after pluggin in the device again.
This behavior happened after upgrading pipewire to version 0.3.43. Not noticed before version 0.3.43. Before pipewire 0.3.42 I was using pulseaudio.Maybe the problem could depend also on the kernel upgrade.

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

Steps to reproduce:

as described above, suspend to memory the machine then go to firefox and try to play sound/video, or launch an application that requires audio. Both hang until the USB audio device (https://www.amazon.com/UGREEN-External-Converter-Adapter-Desktops/dp/B06XP5R449/ref=sr_1_36?crid=2L308NPH93CS7&keywords=ugreen+audio&qid=1642327013&sprefix=ugreen+audio%2Caps%2C185&sr=8-36)
is disconnected.

This task depends upon

Closed by  David Runge (dvzrv)
Saturday, 19 February 2022, 12:50 GMT
Reason for closing:  Upstream
Additional comments about closing:  This is an upstream issue (e.g. https://gitlab.freedesktop.org/pipewire/ pipewire/-/issues/2001)
Comment by Mark Blakeney (bulletmark) - Monday, 07 February 2022, 22:50 GMT
@jamp, I suspect this may not be related to pipewire but rather to the kernel upgrade to 5.16 which occurred a few days before you raised this bug. Install the LTS kernel (5.15.*) to check if this problem goes away? See https://bbs.archlinux.org/viewtopic.php?id=273469.
Comment by David Runge (dvzrv) - Tuesday, 08 February 2022, 17:24 GMT
@jamp: Thanks for the report.

I don't believe this is a packaging related though and this issue should be reported upstream (e.g. https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2001).
Comment by Jamp (jamp) - Thursday, 10 February 2022, 07:07 GMT