Some middle-aged guy on the Internet. Seen a lot of it, occasionally regurgitating it, trying to be amusing and informative.

Lurked Digg until v4. Commented on Reddit (same username) until it went full Musk.

Was on kbin.social (dying/dead) and kbin.run (mysteriously vanished). Now here on fedia.io.

Really hoping he hasn’t brought the jinx with him.

Other Adjectives: Neurodivergent; Nerd; Broken; British; Ally; Leftish

  • 0 Posts
  • 3 Comments
Joined 2 years ago
Cake day: August 13th, 2024
  • palordrolap@fedia.iotolinuxmemes@lemmy.world•systemctl status --user pipewire
    0·
    23 days ago

    Pipewire is newer and emulates PulseAudio so that it can be used as a drop-in replacement. There’s literally a command called pipewire-pulse related to this.

    It makes me wonder if they really have both installed or are mistaking Pipewire’s emulation for an active PulseAudio installation, and so it’s just Pipewire that’s acting up.

    I’d say reboot, but being in space might be one of those times where that’s a non-starter. In which case, they’re going to have to get their hands dirty unpicking system hooks and trying to reattach them all again as and when Pipewire’s working again, assuming it doesn’t do that automatically.

    I never had a problem with either Pipewire or real PulseAudio back when that was current. I had motherboard sound physically pop, requiring the purchase of a separate sound card, but never a driver issue, so I can’t even imagine what might be going on.