• corsicanguppy@lemmy.caEnglish
    0·
    2 months ago

    Wow. I’ve just stepped out of the office for a rage break because pipewire shat the bed again. It’s amazing how sound seems to be a solved problem 5 or 10 years ago but now it’s just offal.

    • FauxLiving@lemmy.world
      0·
      2 months ago

      That’s not a pipewire problem, that’s a systemctl problem.

      Failed to connect to user scope bus via local transport: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined

      The error means systemctl --user can’t reach your user’s D-Bus session because the required environment variables aren’t set. This typically happens when you’ve switched users via su or sudo rather than logging in directly, because htose don’t initialize a full systemd/PAM session. It could also be that your session wasn’t properly initialized by systemd-logind or a number of other things. Try spawning a proper user session:

      sudo machinectl shell your_username@

      and try the systemctl command again.

      • corsicanguppy@lemmy.caEnglish
        0·
        2 months ago

        typically happens when you’ve switched users via su or sudo rather than logging in directly,

        1. I wish typical scenarios were the only ones we had – it’d be a trivial solution.
        2. This is a largely unmolested install because I don’t want to be debugging my desktop. If I had a point other than whingeing, here, that would be it: when the default, vanilla, least-tuned setup falls over on the regular, then it’s fundamentally a failure at its “you had one job” task.
    • nroth@lemmy.world
      0·
      2 months ago

      Yeah, it was working fine but then it got really hard to use pulse. Just when it was stable, we get a few good years before having to switch to a new unstable thing, since pulse lost support.

        • The_Decryptor@aussie.zoneEnglish
          0·
          2 months ago

          Depending on the output device it’s still using ALSA underneath (e.g. Bluetooth output instead is given to the BT stack), PipeWire is dealing with managing and routing the audio output rather than actually performing it.

    • buddascrayon@lemmy.world
      0·
      2 months ago

      I have it piping audio to three different devices at the same time. And believe it or not they’re all in sync… most of the time.

  • ☂️-@lemmy.ml
    0·
    2 months ago

    fake. pipewire is actually awesome.

    that nagging sleep issue though? yeah…

    • corsicanguppy@lemmy.caEnglish
      0·
      2 months ago

      actually awesome

      It shits the bed about weekly for me. I’m glad it’s working reliably for someone.

      • ☂️-@lemmy.ml
        0·
        2 months ago

        pipewire was actually the magic end of all my audio issues on all my computers. what kind of setup do you run?

    • Baggie@lemmy.zip
      0·
      2 months ago

      Sleep is my favourite function to complain about, it breaks shit at random on windows and Linux, nobody seems to know why or how. The fact that sleep works as well as it does on consoles and steam deck is a miracle to me.

  • Nalivai@lemmy.world
    0·
    2 months ago

    This is psyop, they run windows up there, their outlook doesn’t work, and everyone kinda accepted that.

    • lightnsfw@reddthat.com
      0·
      2 months ago

      I hope that’s like a personal laptop or something. I’d hate to think we shot people into space on something that’s running windows for a critical system.

      • MajorasMaskForever@lemmy.worldEnglish
        0·
        2 months ago

        I have not worked on human rated launch vehicles, but I’ve been adjacent to them, saw what went into them, and a few close personal friends have worked it.

        Anything that can jeapordize the safety of the crew must go through a rigorous independent validation and verification process that takes years, software included. No shot a Microsoft product was even in consideration for those systems.

        Being in industry I find it crazy that so many people are freaked out by this. Astronauts have email, they have tasks and schedules and reports to make. Why would NASA reinvent the wheel on a task/schedule manager when the ground operators and astronauts are already used to using Outlook.

          • UnimportantHuman@lemmy.ml
            0·
            2 months ago

            I think they’re saying they’re not using Windows to operate Artemis II but the astronauts are probably used to using Microsoft products. So when it comes to simple logging and data entry they probably are using Windows. But these are their own computers and not used to run Artemis II. I may be wrong but that’s how I understood it.

            • MajorasMaskForever@lemmy.worldEnglish
              0·
              2 months ago

              Yup, sometimes it’s too easy for me to just slip into work mode when talking about this kind of stuff and I don’t elaborate enough. Thanks for stepping in.

              Based on industry rumors I believe the Orion capsule control computers are running VxWorks (I’ve heard that maybe a few boxes are using RTEMS?) All of that source code would have been reviewed, audited, and tested to hell and back.

              The day-in-the-life stuff for the astronauts is entirely believable to be Windows. The risk of it failing is so low (medium probability, low impact), it’s what they’d be familiar with, and it’s part of daily life at NASA anyways. Linux is no better when it comes to safety critical components and the astronauts almost certainly wouldn’t want to be dealing with Gnome’s… uniqueness…

        • cannedtuna@lemmy.worldOPEnglish
          0·
          2 months ago

          While I don’t disagree, given there was a user making throwaway accounts solely to post controversial comics on !comicstrips@lemmy.world, this is a pretty specific joke that only Linux users would understand and appreciate. It of course is parodying the 2 instances of outlook issue they had on the rocket.

          • Nalivai@lemmy.world
            0·
            2 months ago

            Yeah, I don’t actually believe all of that jokes are literally psyop. It wasn’t entirely serious comment.
            It wasn’t entirely unserious either.

  • epicshepich@programming.dev
    0·
    2 months ago

    My laptop is Mint and it’s never given me audio issues. My gaming rig is Nobara and the only audio issue I’ve had with it is that I forgot to switch the output to the TV.

  • Tanoh@lemmy.world
    0·
    2 months ago

    I actually had a sound issue the other day. Just no sound, how weird. It worked the day before. Checked wpactl, volumes etc, everything was fine and working. Restarted pipewire, still no sound.

    Turns out my external mixer lost power because the powet socket was slightly loose.

  • Buddahriffic@lemmy.world
    0·
    2 months ago

    Anyone have any idea how to troubleshoot my motherboard’s HD Audio device just not showing up at all in my hardware devices? I’ve made sure it’s enabled in UEFI settings but it just appears to not even be enumerated by the hardware scan.

    My previous mobo’s HD Audio also didn’t show up at first, but that one fixed itself by the time I came around to troubleshoot it (maybe an update?). Had to replace that mobo because of hardware damage, but I didn’t bother reinstalling the OS as I didn’t think it was necessary.

    Other then hoping the next round of updates resolves this, I’m out of ideas.

  • grue@lemmy.world
    0·
    2 months ago

    Real talk, though: why has Linux taken at least five tries (OSS, ALSA, JACK, PulseAudio, PipeWire) to get audio right?!

    • Rose@slrpnk.net
      0·
      2 months ago

      Ohhhhhh the newbies don’t remember EsounD (Enlightenment Enlightened Sound Daemon). Basically, it was an attempt at doing PulseAudio-esque stuff way back in the OSS era. Which is to say, it just supported software mixing of multiple audio sources, because OSS usually only allowed single process to output audio. EsounD was janky and didn’t work well, obviously. Probably the neatest thing about it was that it exposed the mixed output stream to any other app, so that made visualisers much easier to make (edit: another thing that newbies in this day and age don’t realise, but I cannot emphasise enough how crucial visualisers were for the late 1990s / early 2000s music experience). ALSA basically supported hardware mixing (if available) out of the box, so of course it immediately became my favourite.

    • Something Burger 🍔@jlai.lu
      0·
      2 months ago

      OSS came first, then got replaced by ALSA after it became proprietary.

      PulseAudio is a userspace audio server to which programs connect. It manages audio settings per app, then sends everything to ALSA. JACK is the same but with a focus on low latency.

      PipeWire is a modern drop-in replacement for both, and also has support for video on Wayland.

      • heliotrope@retrofed.comEnglish
        0·
        2 months ago

        And then there’s also sndio, ported from OpenBSD. This does basically the same thing as OSS/ALSA.

    • SorryQuick@lemmy.ca
      0·
      2 months ago

      They don’t have the same goals.

      JACK is for professional audio.

      OSS and ALSA are kernel audio drivers, they’re the most powerful of them all but extremely low level. Everything else, like pulseaudio/pipewire are just higher-level interfaces that feed ALSA audio.

      Pulseaudio and pipewire are sound servers.

      So really it only took two tries:

      OSS -> ALSA

      Pulseaudio -> Pipewire

  • tjhrulz@lemmy.world
    0·
    2 months ago

    I feel this one. Used to daily drive Linux but due to a work requirement had to switch to Windows several years back. Windows has been getting shittier and shittier and I no longer need to use Windows for work and it only just gets shittier so I just switched to CachyOS and love it. Except the one and only issue I haven’t been able to fix is audio. I use a Bluetooth speaker on my computer and it cuts out randomly even using low bit rate audio streams. Tried switching pulseaudio to pipewire because the internet said I could increase the latency and that that would fix it but no dice.

    • MonkderVierte@lemmy.zip
      0·
      2 months ago

      Hm? Removed pulse, installed pipewire-pulse, ran pipewire && wireplumber && pipewire-pulse as user and everything just works. Except that my cheap bt-inear sometimes cause a crash of bluetoothd (and that one should restart by itself but whatever) but that’s not pipewire’s fault.

      • mittorn@masturbated.one
        0·
        2 months ago

        @MonkderVierte @tjhrulz
        Hm? Removed pulse, installed pipewire-pulse, run pipewire && wireplumber && pipewire-pulse as user and got no available sound devices.Why? Because wireplumber’s bullshit crashed after forking to daemon.
        With reference pipewire-media-session everything worked, but everybody forcing unstable and bloaty wireplumber, making old configuration not supported…
        Yes, maybe it’s not pipewire fault, just it’s modular architecture, but it makes me unhappy with it, so i still using jack

    • utjebe@reddthat.comEnglish
      0·
      2 months ago

      Some Mediatek chips are doing this, that is bt audio cutting out while WiFi doing things. Nothing fancy, 1080p video on YouTube will cause that.

    • palordrolap@fedia.io
      0·
      2 months 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.