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

all 23 comments

sorted by: hot top controversial new old
[–] 14 points 8 months ago (6 children)

Save yourself the time and boot into a live distro with gnome, like the latest Ubuntu or something. Sanity test. Make sure it works there before trying to fix your own install.

  • source
  • hideshow 6 child comments
  • [–] [S] 3 points 8 months ago (4 children)

    Live USB - works fine

    Fresh install - works fine

    Update system after fresh install - breaks again

  • source
  • parent
  • hideshow 4 child comments
  • [–] 1 point 8 months ago (3 children)

    Well that's a relief. Dmesg? Journal? Pavucontrol? Might be changing the sound profile or something. Time to have a tinker and inspect. It's 530am here so I'll check back in a few hours

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 3 points 8 months ago* (last edited 8 months ago) (2 children)

    pavucontrol works but it’s annoying to use, I just want to be able to quickly select between audio outputs in the GNOME menu as always.

    alsamixer does not even see any analog output and

    cat /proc/asound/devices

    cat /proc/asound/cards

    cant see any analog output either.

    I can force it with wireplumber when manually selecting correct sink which in system settings defaults to HDMI but audio goes trough my speakers until I need to change output and want to change back. If I manually select HDMI it just goes into my monitor speakers as it should

    edit1

    I’ve just installed CachyOS GNOME and the same issue occurs like on Fedora. Seems like this is either GNOME issue or something with the more recent update…. I’m gonna try OMARCHY

    edit2

    works in Omarchy, I’m gonna try Fedora KDE now

    edit3

    KDE works but I can’t stand it

    edit4

    I think I figured it out… is this a bug then?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 8 months ago (10 children)

    I have a stupid question: Are you sure you're not confusing "line out" and "headphone out"? They're different, and pretty much every desktop supports both these days. But standard PC speakers usually connect to the "headphone" socket.

  • source
  • hideshow 10 child comments
  • [–] 4 points 8 months ago (8 children)

    I am seeing the exact same issue on a PC I just put together and loaded Fedora 43 Workstation on. If I hook the 3.5mm jack for the speakers (older Creative Pebbles) to the green port on the back panel it shows up just like OP's when I try to test; however, if I plug the jack into the headphones port on the case (which is connected to the motherboard audio pins) it detects and works properly. I was also seeing some Dummy Output options with the line out connection in use, and not knowing what it meant, I selected one and this kicked me back to the login screen and gave me an unhelpful kernel alert.

    In contrast, the speakers on my other PC, which is also running Fedora 43 Workstation, works fine off of the back panel. Both motherboards are using Realtek audio chips but it may not be the same version since one board is a B650 and one is a B550.

    Curious to see what the solution ends up being but I also recently installed pavucontrol on the newer PC so I will try and set the speakers up using the line-out that way. If that doesn't work I will migrate to bluetooth speakers or just leave things as is.

  • source
  • parent
  • hideshow 8 child comments
  • [–] [S] 2 points 8 months ago (4 children)

    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

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 8 months ago (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] [S] 2 points 8 months ago (2 children)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 7 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 8 months ago (1 child)

    Hmmm. Random guess: does your machine have another audio output, possibly via HDMI, that you're not using? This could be ALSA selecting the wrong device as a default, which would then propagate up through the stack.

  • source
  • hideshow 1 child comment
  • [–] 1 point 8 months ago (1 child)

    Try using alsamixer, check for channels that are muted.

    Also check if your distro is saving and restoring alsa settings every boot and remove the settings file

  • source
  • hideshow 1 child comment
  • [–] 1 point 8 months ago

    I'm currently learning about it, so I can't offer much expertise, but if all else fails, look into Wireplumber; it sounds like it's failing to make the proper node connections automatically.

  • source