Potential fix for audio issues

Ask Fedora
, ,
1

This is in relation to an older thread by another user.

Struggling with the same dilemma on now Fedora 40, I was uneasy to follow the solution done by the OP since modifications in the package target directory will be reverted by any software update of that package.

The alternative solution on that thread appears to no longer work since the referenced file does no longer exist.

Looking high and low I found a closed issue where the Wireplumber project owner posted the preferred solution.

Essentially:

  1. Create the file (and path) /etc/wireplumber/wireplumber.conf.d/disable-idle-timeout.conf
  2. Add the following content to it:
monitor.alsa.rules = [
  {
    matches = [
      {
        ## Matches all sources.
        node.name = "~alsa_input.*"
      }
      {
        ## Matches all sinks.
        node.name = "~alsa_output.*"
      }
    ]
    actions = {
      update-props = {
        session.suspend-timeout-seconds = 0
      }
    }
  }
]
  1. Restart Wireplumber (systemctl --user restart wireplumber.service)

I hope that helps more people facing the same issue.

2

You should use your own thread.
Posting on a necro thread that is at least 5 release versions old is not helpful since almost everything has been updated or otherwise changed in that time. f40 is much different than f35 was

I moved your post to a new thread so it receives the attention it deserves (It will still be linked to this thread (which I am closing))

3

Thanks! I was contemplating about doing exactly that and in fact started out with a new thread. However, it felt like duplicating the previous one, potentially confusing people coming across either the old or my thread. So, I decided to add it underneath the other thread to keep it neatly together in one place, giving people a better picture on potential solutions.

In the end the idea and background is exactly the same as the OP of the older thread. Apart from software updates (and some file rearrangements), nothing really changed.

4

No problem
I just felt that it was appropriate to have the new thread for the current version and there are many differences in the software over the last 5 releases.

Your post is confirmation that the older solution is still relevant.