The last two upgrades have broken my audio setup.

First the options for Network Server and Network Access in paprefs were greyed out and my sinks disappeared after upgrading to bookworm. I just had to create a link to an existing file and it was working again but, it’s weird that it was needed in the first place. Pretty sure it has something to do with the change from pulseaudio to pipewire but I’m not very up to date on that subject and I just want to have my current setup to continue working.

Then yesterday I just launch a simple apt-get upgrade and after rebooting my sinks disappeared again. The network options in paprefs were still available, but changing them did nothing. I had to create the file ~/.config/pipewire/pipewire-pulse.conf.d/10-gsettings.conf and stuff it with “pulse.cmd = [ { cmd = “load-module” args = “module-gsettings” flags = [ “nofail” ] } ]” in order to have my sinks back.

I know it’s not only a Debian thing, as I can see this happening to people on Arch forums, but as Debian is supposed to be the “stable” one, I find it amusing that a simple upgrade can break your sound.

  • cley_faye@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    6 months ago

    Not at all. I’m arguing that often, the issues, and fixes, are not distribution-dependant. Which is a good thing; it means we can go to arch forum and find fixes that can be applied in other distros most of the time, for example.

    But people keep pitting them against each other like they’re some form of evolved lifeforms that necessarily have to erase others, when a lot of the issues are just generic software issues.

    And, since this is already a justification post I’ll take the lead and note that it does not mean that there is no distribution-specific issues. Of course there are. The point is that most software issue in distribution X will have the same cause and fix in distribution Y, and often have nothing to do with either specific distributions.

    • bitwaba@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      Yeah, the difference in distributions is that even though there’s a fix on the Arch wiki that solves the Debian issue, Debian shouldn’t have released the update in the first place.