This is not a question per-se but more of a break down of my original issue and the solution.
I recently decided to feel adventurous and jump on the rawhide bandwagon with my laptop running F34 plasma. So as all intrepid explorers do, I promptly performed a dnf system-upgrade and off it went. After approx 1 hr the system had rebooted and installed the necessary.
The system boots and I log in, everything is looking great until I look at the task bar and notice the red strike through the audio indicator. I click this and āno sound devices detectedā hmm is this the 5.14 kernel or something elseā¦oh well no time to troubleshoot, put it away.
Today I decide to look a bit deeper, lspci -v showed that the audio device was there and that a module was loaded for it. Typing pactl info showed the pipewire-pulse item was available, but a pactl list sinks short showed nothing. I went into alsamixer which showed that the sound card was literally there as expected, I could modify the volume settings etc.
Long story short, a quick internet search and a trip to the faithful Archwiki pipewire page later the solution was staring me in the face:
āa new systemd service has been added which is disabled by default, meaning there is no pipewire-media-session running on system startā
Sure enough, systemctl --user status pipewire-media-session showed pipewire-media-session was disabled and not running, so systemctl --user enable pipewire-media-session && systemctl --user start pipewire-media-session being the logical next step thatās what I did and suddenly the audio icon changed back to normal showing the device was there and ready for use.
So the whole point is, for future reference when F35 comes out hopefully this issue will be resolved, but at least you have one possible solution in the meantime.
true. well i probably should have read up on the changes there, but still i feel like the upgrade process should obsolete pipewire-media-session if thatās the proposal
I think that this is covered under the āScopeā section of the change proposal:
Release engineering: A new systemd service will need to be activated in the default install.
Since F35 has just branched, itās not surprising that this hasnāt landed yet. I would prefer that we get to a place where people arenāt dropping these changes into Rawhide without all the parts lined up, though.
After reading that wireplumber was the accepted replacement in the post above by @grumpey and how to switch pipewire-media-session to wireplumber from the change proposal, I installed wireplumber and tested that general audio worked as expected, which it did.
Currently, Fedora 35 Beta uses wireplumber and the system should switch to it automatically when being upgraded. There have been some flaws recently, that wireplumber was not installed by default and pipewire-media-session had to be restarted manually in early upgrades, but this should be gone now.
Thank you very much for the quick easy fix. I think that it is just not the real fix of the issue and we will have to revert back to wireplumber when it gets fixed.
I just want to add that this issue is happening in the released version of Fedora 35 and is very inconvenient.
Seconding this - did the F35 release upgrade last night, looked ok but didnāt use it until this morning then found no sound devices listed.
Agree that the switch over ought to work straight away, or they should not bother until it is sorted.
I should add that I run the Cinnamon desktop by choice, as an addition to the originally installed Gnome. I tested in Gnome before finding this post, then after doing the DNF commadn, switched back to my preferred Cinnamon DE with sound now working again.
The wiki page says to enable and start the wireplumber service https://fedoraproject.org/wiki/Common_F35_bugs#No_sound_after_upgrade
but this didnāt solve it for me, i fixed it by commenting out the # { path = "/usr/bin/pipewire-media-session" args = "" }
line close to the end of /etc/pipewire/pipewire.conf file and reboot.
I also deleted everything in the ~/.config/pipewire folder, but i think that isnāt neccessary.
Edit:
If this is a common issue, it would be nice if someone could add it to the āNo sound after upgradeā section in the F35 Common Bugs page.
This is just needed if you have made some changes for your selves. A configuration who is different from the default.
The default config files are in /usr/share/pipwire/ this was already communicated in the change-log wiki of F34
Is there a bugzilla about it? I couldnāt find any. It has failed for me on two out of two updgrades. The wireplumber RPM gets installed, but the service is disabled, even though the preset is āenabledā.