this post was submitted on 04 Apr 2026
880 points (96.7% liked)

linuxmemes

31120 readers
172 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    880
    systemctl status --user pipewire (lemmy.world)
    submitted 2 weeks ago by cannedtuna@lemmy.world to c/linuxmemes@lemmy.world
    130 comments fedilink hide all child comments
     

    you are viewing a single comment's thread
    view the rest of the comments
    [–] corsicanguppy@lemmy.ca 16 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

    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.

    edit:

    $ systemctl status --user pipewire
Failed to connect to user scope bus via local transport: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)

    wheeeee

    [–] FauxLiving@lemmy.world 9 points 2 weeks ago (1 children)

    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.ca 1 points 2 weeks ago (1 children)

    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.
    [–] FauxLiving@lemmy.world 1 points 2 weeks ago

    If it's consistently breaking then your distro is messing up something. Bad defaults, broken scripts, etc.

    The problem is that the environment variables are expected to be there and they are not there.

    So, if you're not doing something odd, then your distro is pushing misconfigurations or some other piece of software is interfering with your environmental variables. Whatever the vanilla setup for your distro is, it is not setup correctly.

    I do agree that it's frustrating, just aim the ire in the right direction... whoever configured your system's defaults.

    [–] nroth@lemmy.world 1 points 2 weeks ago (3 children)

    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.

    [–] CrypticCoffee@lemmy.ml 1 points 2 weeks ago

    I used to have crackling issues with pulseaudio. It needed restarting constantly. Not issue since the switch to pipewire. So my experienced was the absolute opposite of yours.

    [–] corsicanguppy@lemmy.ca 1 points 2 weeks ago

    it got really hard to use pulse

    Pulse was another tumour by Lennart. I have no regrets in its passing.

    [–] WhiskyTangoFoxtrot@lemmy.world 1 points 2 weeks ago (1 children)

    I never understood why we didn't just stick with ALSA. OSS was crap, certainly, but ALSA seemed to do the job.

    [–] The_Decryptor@aussie.zone 5 points 2 weeks 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.