pipewire in rawhide isn't working for me, no sound. Any pulseaudio / pipewire migration links welcome.
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. I can play sound using aplay, so I know that the underlying alsa infrastructure is working. Somehow I ended up with both pipewire and pulseaudio installed. When I try to remove pulseaudio, it wants to take a lot of packages with it. Trying to remove pipewire takes fewer, but, as the new standard, I want to keep it and get it working the way I want.
So, I'll be doing web searches for help, but are there canonical help documents that someone can point me to for help with the migration from pulseaudio to pipewire?
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.
On Fri, 02 Jul 2021 14:36:32 -0700 Adam Williamson adamwill@fedoraproject.org wrote:
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.
It is indeed pipewire-0.3.31-1.fc35. Thanks.
On Fri, 2 Jul 2021 16:48:26 -0700 stan via test test@lists.fedoraproject.org wrote:
On Fri, 02 Jul 2021 14:36:32 -0700 Adam Williamson adamwill@fedoraproject.org wrote:
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.
It is indeed pipewire-0.3.31-1.fc35. Thanks.
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 06:22:54 -0700 stan upaitag@zoho.com wrote:
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.
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.
On Sun, 4 Jul 2021 07:38:08 -0700 stan via test test@lists.fedoraproject.org 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.
Hello Stan,
I would say that switching to PulseAudio from PipeWire on F35 is an ugly hack that you should try to avoid as much as possible. On Fedora 34, PulseAudio was replaced by PipeWire which is the default sound solution for Fedora 34. This is the same for Fedora 35.
If you are having problems with PipeWire on F35, it might be worth troubleshooting that rather than going back to a deprecated solution, especially when there were no audio issues on Fedora 34 when we released, and I have not seen any since then either.
On my Fedora (34), I do have the /etc/pipewire location where the configuration files for my system are stored. Also, there are two services which need to be running at least, pipewire and pipewire-pulse. I am using pavucontrol to tweak the connections, but Gnome Settings could do, too.
I will try installing F35 later today and see if I experience any troubles with the sound.
Stay tuned. Lukas
On Mon, Jul 5, 2021 at 4:20 PM stan via test test@lists.fedoraproject.org wrote:
On Sun, 4 Jul 2021 07:38:08 -0700 stan via test test@lists.fedoraproject.org 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@lists.fedoraproject.org To unsubscribe send an email to test-leave@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
How to trouble shoot?
I tested the following kernels with fully updated F35 and Gnome-Settings->Sound shown no sound devices:
vmlinuz-5.12.0-198.fc35.x86_64 vmlinuz-5.13.0-0.rc6.20210617git70585216fe77.48.fc35.x86_64 vmlinuz-5.13.0-58.fc35.x86_64+debug vmlinuz-5.14.0-0.rc1.20210714git40226a3d96ef.18.fc35.x86_64 vmlinuz-5.14.0-0.rc2.20210721git8cae8cd89f05.24.fc35.x86_64
While the following kernel w/ F34 are all having sound: vmlinuz-5.12.15-300.fc34.x86_64 vmlinuz-5.12.17-300.fc34.x86_64 vmlinuz-5.13.4-200.fc34.x86_64
I find this in bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1983861
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.
Sound is working normally after starting pipewire-media-session
-
Adam Williamson -
Lukas Ruzicka -
Sampson Fung -
stan