00:01 <elderK> Hey guys, is there any real reason I should switch from pulseaudio to pipewire if pulse seems to be working okay?

00:04 <farkuhar> elderK: pipewire is needed if you ever do screen sharing on wayland. But I recall that you're hesitant about diving into wayland, so screen sharing there won't be a compelling reason for you.

00:07 <elderK> I'm just looking for real reasons to justify moving away from Xorg. I mean, everything here is working pretty well for the most part.

00:07 <elderK> I'm also very comfortable with my WM that I use - and I don't know whether I'll be able to continue using that in Wayland.

00:07 <elderK> Pipewire, being an audio only change, might be worthwhile, if it's better in some way that I can make use of :)

00:07 <elderK> I figure pipewire will eventually replace pulse so it might be worth learning at some time.

00:08 <elderK> It's like systemd - I have yet to really learn that because I generally avoid distributions that use it. I expect that to change one day, though.

00:16 <farkuhar> The early versions of pulseaudio were too broken for some users. Pipewire seems to have avoided those missteps, but the constant changes to its ABI and config files makes it feel like a moving target. I had to rebuild qutebrowser and firefox after the latest pipewire upgrade in order to have sound in my browsers again.

00:17 <elderK> I'm using firefox-bin and thunderbird-bin, mostly to avoid the massive build times.

00:27 <groovy2shoes> elderK, if your setup is working and you feel comfortable, there's no real reason to move away

00:31 <groovy2shoes> as far as benefits of wayland, i'm no expert, but the gist of it is that X11 was designed at a time when everyone was connecting to multi-user machines, a time before everyone had a GPU, and as a result the Xorg display stack isn't quite as nice on modern machines as it could be. inefficiencies and whatnot.

00:45 <elderK> How stable and stuff is Wayland these days? Is it at a point where you can rely on it?

00:48 <mechaniputer> elderK: Looks like several major distros default to it for Gnome, including Debian. So if you use Gnome it's probably decent enough.

00:50 <mechaniputer> elderK: Apparently several of my machines are using pipewire, but none are using Wayland. I haven't noticed pipewire causing any problems for me.

00:51 <mechaniputer> (Pipewire on Void and Debian, plus one work machine on Fedora)

00:53 <mechaniputer> Hmm. Maybe not on Void after all. Guess I misremebered.

01:01 <elderK> I have a Debian system for work and it's moved to pipewire. It's probably always been running pipewire although I've only encountered issues in the past week with pacmd. Maybe pulse was retired as part of an update.

01:10 <SiFuh> https://docs.voidlinux.org/config/media/pipewire.html

10:44 <cruxbot> [opt.git/3.6]: tcsh: update to 6.23.00

10:44 <cruxbot> [opt.git/3.6]: mailx: update to 14.9.23

10:45 <cruxbot> [core.git/3.6]: elfutils: update to 0.186

12:22 <pedja> frinnst, rejoice https://gitlab.freedesktop.org/xorg/xserver/-/issues/1241

12:22 <pedja> (dpi breaking change will be reverted in next xorg release)

12:23 <pedja> nice idea, but apparently pretty much all gui toolkits presume/expect 96dpi

19:41 <cruxbot> [contrib.git/3.6]: nawk: up to 2021-11-03

20:02 <frinnst> pedja: I only noticed it with qt5 stuff. granted, I dont use a lot of programs these days

20:04 <pedja> ah, ok

20:05 <pedja> it's funny, though. xorg starts doing the right thing™️, and all hell breaks loose(apparently) :)

20:06 <frinnst> heh well since they have been doing it wrong for donkeys years, people adapted :-)

20:07 <pedja> pretty much. and since it's on borrowed time, or as release manager said 'wayland is around the corner', no one will be bothered to fix the breakage

20:08 <pedja> well, maybe qt will, think I saw a mention of the bug opened there

20:09 <pedja> afaict, using monitors with various dpi's isn't an exotic thing to do these days, so that should be fixed anyway, wayland or no wayland

23:37 <cruxbot> [opt.git/3.6]: nvidia: updated to version 470.86

23:37 <cruxbot> [compat-32.git/3.6]: nvidia-32: updated to version 470.86