They're not supposed to have both installed.

Systemd just keeps asking me for govt id, I didn't bring it with me to space

Thanks Dylan

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.

I'm pretty sure this is a meme based on the real report that they had 2 instances of outlook on windows and not real.

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

That’s the thing about open source. Someone always thinks they can do better

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.

Wait, they had two instances of not real? They are learning too much.

Sorry I am autistic and often don't know how to properly formulate my thoughts into sentences :D

This is a joke right? Yesterday I saw a post that outlook was a problem for them

Relevant

wdym?

Astronauts are following the same photo format as they've always done, and the penguin is wearing a tuxedo.

Yes it’s a joke referencing the two Outlook instances issue, but for Linux people

Haha thanks. I feel dense in retrospect

Sometimes satire is hard to detect in this joke of a reality we’re living in.

The image looks like the contrast was increased too much for unknown reasons.

Ain't that the truth. Have a good evening!

Funny thing, but it's windows I got problem sound problems with. Randomly decide to ignore mic, speakers doesn't get out of "phone call quality mod". Every time I need to disconnect then reconnect just for my colleagues to hear me out.

Linux? No problem. Easy effects run perfectly too (except when low CPU availability... But everything at that point gets problems)

Huh.

To me it looks like an actually very well colorbalanced photo... maybe something to do with image formats, different kinds of viewing devices, some kind of HDR process working oddly?

EDIT:

Also, the background, the backdrop, its ... the actual pattern of the material is that its lighter and more colorful in the center, and then does a kind of noisy circular taper to black, toward the edges.

Thats not an exposure or contrast error, its an intentional choice, meant to emphasis the center of the image, but also allow the well lit people on the edges to be clearly discernable, in detail.

Its a fairly common practice in more traditional portrait photography.

I think the answer is that slop tends to make everything look well lit and soft like a portrait. So by association, portraits now look like slop.

Yeah I guess that is actually what is happening... combined with... 99% of pictures people see these days are taken with phones or webcams, with different methods of doing color balancing, and different standards for lighting and color grading.

Whereas it used to be, in the before days, in the last century... you'd probably most often see a person pictured in either a school photo, a mugshot, a portrait done for some other occasion, or basically a polaroid, which would be recognizabley differently exposed/styled (basically) from the rest.

Dad, don't do this in front of my friends. You're embarrassing me.

What the hell linux distros are so far back in time that they have audio issues? I haven't had to do anything in maybe the past decade and even when distro hopping it always worked?

Or is it super niche hardware? I haven't heard of any real people using anything other than mobo built in audio since like 2007.

I'm still waiting for the latency to be viable for playing guitar with an audio interface.

It’s a joke about the two outlook instance issue

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

"lol it's just satire" meanwhile people are thinking audio, gaming, whatever is an issue on linux
as a few year old linux convert, getting used to it is the biggest hurdle

I mean sure but, like... 2005 called, they want their mail order ubuntu cd back.

I just installed Pop!_OS this week and have this problem constantly. The point I had to write a service to watch for all my audio devices to vanish and restart the others.

That's not a feature thats exclusive to open source though. Circular reasoning like this just distracts from the fact that software just like hardware is constantly evolving, even in personal spaces. Thinking someone can do better has no relevance on the "open source" aspect or the political leaning.

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.

Being in IT with windows 11 is awful.

"Why isn't my mic/audio working?"

Me: "Idk, restart the computer"

"That fixed it. I don't understand, it was just working yesterday. Why did it stop working?"

Me: "Windows 11 sucks..."

Not to mention how awful it is being in a teams call as the IT guy and my mic isn't working because, again, windows is ass

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

actually awesome

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

You mean someone thinks they need to do better not by enhancement but by complete replacement. See: Systemd and its own flailing.

I'm using pipewire just fine to do so? I just needed to set the buffer size to something appropriately low and I've had no issues from popewire's side

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.

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

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.

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.

For we all live underground

Holy audio

SystemD knows what it has to do.

Can't believe Linux would do such a thing

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.

My pipewire seems to have issues with crackling audio and severely dampening my mic and I have no clue why.

Still better than Windows.

I'm still trying to figure out why the only real way of taking screenshots fast in Wayland is to do a video capture of the desktop with pipewire...