I updated my system and media-video/pipewire updated from 0.3.36 to 0.3.49-r1 No sound after login in my GNOME Session. (PC and VM, so reproductible issue) I used to use pulseaudio. Killing manually pipewire process restore sound. Or adding exit 0; at begening of /usr/bin/gentoo-pipewire-launcher script. Reproducible: Always Steps to Reproduce: 1. Install system with pulseaudio and masking pipewire > 0.3.36 2. Unmask pipewire and upgrade system 3. See the issue. Actual Results: No sound Expected Results: Sound OK
Created attachment 773444 [details] emerge --info media-video/pipewire
Cross-linking thread for reference: https://forums.gentoo.org/viewtopic-t-1148819.html
What happens if you edit /etc/pulse/client.conf to say this: autospawn = no Please reboot after making the modification (and of course undo the exit 0 modification you made to the launcher script). If that helps, perhaps it's time to just fast track replacing PulseAudio with PipeWire.
In case if after reboot there is still no audio, then still with autospawning disabled please try to manually run gentoo-pipewire-launcher and see if that restores audio.
I tried : autospawn = no + enable again pipewire script. Sound is here, i can listen audio but sound crackling, recording sound with a mic plugged is USB don't work. Pipewire isn't stable in the real life, so i want keep pulseaudio and don't use this Pipewire
Thank you for verifying that disabling autospawning fixes audio. I'm not immediately sure why PipeWire is now even more prone to interfere with PulseAudio than previousl. But, as I have pointed out even before the XDG launcher script was deployed, it was the wrong solution exactly because it could brick the audio partially or fully depending on how the dice roll, so in a sense we just have arrived at what was the predicted outcome. If the crackling is with a USB device, it might help to try a newer kernel such as one of the 5.17 kernels. Alternatively it could be that the particular client is requesting the lowest possible latency and then failing to deliver data on time. In order to isolate the cause of crackling, it might help to test more devices and client programs, if you want and can do so. Another useful tool is to look at pw-top and observe if any of the values in the ERR column go up and which ones the most or in correlation with the crackles.
Finally, crackling is only on OBS not with audacity. It's a config issue with OBS. New clean config of OBS and all is OK
autospawn = no + pipewire script : All is okay !
With the USE=sound-server changes, I think this is sorted now.