On Fri, 2021-07-02 at 11:35 -0700, stan via test wrote: > I am having trouble with sound in a new rawhide installation. I > waited for F35 because I thought the kinks in pipewire would be > worked out, but not so much for me. It might be something simple, > but when I try to turn off cards, and assign cards to default, etc. > it doesn't work. What version of pipewire did you get? pipewire-0.3.31-1.fc35 is known broken. If you got that, get pipewire-0.3.31-2.fc35 instead - https://koji.fedoraproject.org/koji/buildinfo?buildID=1776760 (you'll need to update all installed subpackages). Unfortunately Rawhide composes are failing ATM so even though I did the fixed build two days ago, it's not in the repos yet.

Unfortunately, updating to the latest version did not fix the problem. The fixed version came through with a huge bundle of updates, including a 5.14 kernel. I tried the procedure in https://bugzilla.redhat.com/show_bug.cgi?id=1931384 comment 16, rm -rf /etc/pipewire dnf reinstall pipewire-alsa.x86_64 pipewire-gstreamer.x86_64 pipewire-pulseaudio.x86_64 pipewire systemctl --user restart pipewire pipewire-pulse but it didn't help. There was no /etc/pipewire to begin with, and there is an /etc/pulseaudio. So, I think the system believes it is running pulseaudio, but pipewire is somehow blocking pulseaudio from running correctly even though it can't run itself. I think I will need to remove pulseaudio and all the dependencies it takes with it, then run the above procedure, and reinstall all the removed packages. I'm reluctant to do that, because those packages will probably pull in pulseaudio again, recreating the problem. I'll keep looking for other solutions for a while.

On Sun, 4 Jul 2021 07:38:08 -0700 stan via test <test(a)lists.fedoraproject.org&gt; wrote: > As a test, I removed pipewire, and its dozen or so dependencies. > Sound started working again, and I was able to configure things to my > preferences. I'll keep an eye on pipewire and its progress, perhaps > try installing it and its dependencies periodically, but I don't > really need its touted benefits, so for now I will stick with working > over innovative. The fix didn't survive a reboot. When I checked, it was running pipewire-pulseaudio, not pulseaudio. So, I installed pulseaudio with --allowerasing, and sound is again working. Well, almost. I use an obsolete fedora python2 application that I rebuild locally called pulseaudio-equalizer to tune sound output. And it is not working with the new pulseaudio. If there was a built in equalizer in pipewire, that would provide an additional incentive to get it working. _______________________________________________ test mailing list -- test(a)lists.fedoraproject.org To unsubscribe send an email to test-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

>I think this is entirely normal in f35. The session manager >>is not started by pipewire anymore but by systemd.

>You probably need to manually enable and start >pipewire-media-session with:

>systemctl --user enable pipewire-media-session >systemctl --user start pipewire-media-session

>I believe there is an update to the default policy on f35 >>scheduled. maybe it does not apply automatically for >>already installed components, I don't know.