Speakers -> Worked via Line OUT for months
Take PC apart and change PSU, assemble PC back.
Speakers - Line OUT detected but can’t test Left/Right audio channels, options missing. No AUDIO from speakers unless I select them as default in Pavucontrol or manually assign outputs via Helvum.
Fedora 43 GNOME

How do I get my GNOME audio settings to work again?
This is so random and funny at the same time… yet frustrating because it makes no god damn sense :D


Seems like it’s GNOME issue or something driver issue with more recent update. Fresh install works again until I do a system update then it breaks again. I’ve tried CachyOS GNOME and the same issue again
Hey I tested the downgrade script and it fixed my issue just like you suggested. But of course now my OS wants to update the files back to the version I rolled back from. It doesn’t seem to be a forced update and I updated and upgraded everything before I tried this but I was wondering if the issue will immediately return once I allow the system to go back to version 49.4-1.fc43.
Doesn’t look like there is any way to skip those file updates so I suppose I just need to do the downgrade again if the sound problem returns? Hoping the next revision of gnome-control-center resolves it.
Thank you again for your efforts and information sharing. This is what I love about the Linux community and it is making the transition from commercial slop-ware so much easier.
Yes, right now it’s just a temporary workaround but it seems it’s being worked on.
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3678#note_2672243
Just as an update to this, I noticed that there was a new version of gnome control center (49.4-2.fc43) in the latest update push for Fedora so I took a chance and did the upgrade hoping it would include a fix to this issue. Based on initial testing on my two machines at home which were affected and needed to be downgraded to 49.1-1.fc43, it looks like this new version resolves the line-out audio problem. Thanks again for your efforts to raise awareness of this and your suggested workaround.
Hi, forgot to post update here but yes, this update has resolved issue for me as well!