Audio sink not available for USB headsets until pipewire is restarted
If you are filing this issue with a regular release please try master as it might already be fixed.
Version, Distribution, Desktop Environment: Ubuntu 21.04 with Pipewire 0.3.32
Description of Problem: When connecting a USB headset, only the microphone (source) is available, not the sink. Restarting pipewire will fix the issue until the next reboot.
This was tested with a Sennheiser PC 8 and and a Plantronics 5200 headset. Both have the same issue.
An error in the Pipewire journal appears:
Aug 03 10:32:04 backxp-HP-EliteBook-840-G5 pipewire[2362]: ALSA lib confmisc.c:1281:(snd_func_refer) Unable to find definition 'cards.USB-Audio.pcm.front.0:CARD=1'
Aug 03 10:32:04 backxp-HP-EliteBook-840-G5 pipewire[2362]: ALSA lib conf.c:4745:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
Aug 03 10:32:04 backxp-HP-EliteBook-840-G5 pipewire[2362]: ALSA lib conf.c:5233:(snd_config_expand) Evaluate error: No such file or directory
Aug 03 10:32:04 backxp-HP-EliteBook-840-G5 pipewire[2362]: ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM front:1
Aug 03 10:32:04 backxp-HP-EliteBook-840-G5 pipewire[2362]: 'front:1': playback open failed: No such file or directory
Aug 03 10:32:04 backxp-HP-EliteBook-840-G5 pipewire[2362]: adapter 0x5608830a3d50: can't get format: No such file or directory
Aug 03 10:32:04 backxp-HP-EliteBook-840-G5 pipewire[2362]: usage: node.name=<string>
How Reproducible: Every time
Steps to Reproduce:
- Start Ubuntu with Pipewire. Laptop sound and microphone work as expected.
- Connect USB headset.
- Headset microphone works, audio does not.
- Restart pipewire-media-session, pipewire-pulse and pipewire and the problem disappears until the next boot.
Actual Results:
Headset shows up in pactl list cards
and pactl list sources
, but does not show up in pactl list sinks
and no audio out possible. After restarting pipewire everything works as expected.
Expected Results: This should work right away without the need to restart Pipewire.
A similar issue was already logged, but if I understand the git log correctly, it should have been solved since 0.3.16