Description of problem: After laptop goes to sleep / suspend and wakes up, the sounds are not working any more Version-Release number of selected component (if applicable): pipewire 0.3.32 Kernel 5.13.4-200.fc34.x86_64 How reproducible: Currently happens every time Steps to Reproduce: 1. Have a laptop that has normal sound card + HDMI output 2. Suspend the system 3. Wake it up again Actual results: Sounds are not working any more Expected results: Additional info: - Laptop model: Thinkpad X1 extreme gen 3 - When changing volume with buttons, it says that it's trying to change the volume of 'HDMI / DisplayPort 3 Output', which is wrong, when it's working it says 'Speakers'. /proc/asound/cards 0 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xee000000 irq 17 1 [sofhdadsp ]: sof-hda-dsp - sof-hda-dsp LENOVO-20TK001FUS-ThinkPadX1ExtremeGen3 The HDMI port is not in use - journalctl has some messages propably related to this: pipewire[2643]: (alsa_output.pci-0000_00_1f.3-platform-skl_hda_dsp_generic.HiFi__hw_sofhdadsp__sink-49) XRun! rate:1024/48000 count:1 time:34548453 delay:22 max:22 pipewire[2643]: '_ucm0008.hw:sofhdadsp,4': playback open failed: No such device pipewire[2643]: adapter 0x55d7ab7b03c0: can't get format: No such device pipewire[2643]: usage: node.name=<string> pipewire[2643]: '_ucm000B.hw:sofhdadsp': capture open failed: No such device pipewire-media-session[2673]: error id:87 seq:1090 res:-22 (Invalid argument): usage: node.name=<string> AND alsactl[1756]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA NVidia at 0xee000000 irq 17) alsactl[1756]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6 - Doing 'dnf swap --allowerasing pipewire-pulseaudio pulseaudio' fixes the problem
FEDORA-2021-667b4bfc51 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-667b4bfc51
FEDORA-2021-667b4bfc51 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.