Title says it all. Anyone accomplished this complete removal/replacement? Numerous systemd distros have even well before Pipewire 1.0 and I'm jealous AF.

Nope can't get pipewire to to work on the console. So it's a no go here.

No. Pulse works, why mess with it. If and when Pat decides this should happen then it will happen here (my system) too.

3 members found this post helpful.

Pipewire after latest upodate it not working in my laptop. Pulse audio did work.

I can confirm that 2 more users from discord (unofficially channel) whose dont have account in LQ, having issues with pipewire also.

Thanks for your response but I am aware that casual audio as in onboard chip level of quality and concern, was an important plus for pulse for such users. I mess with it because I despise Pulse as a semi-pro audio guy with thousands invested in my PC sound system. I prefer hard setting as with ALSA and have problems with Pulse's latency in recording and editing anything with audio. Video containing audio is the worst with Pulse. Pulse requires a nerfed JACK and that's an important app for those of us who work in audio. Pipewire does all that quite well.

To be clear, it's fine by me if Pulse stays available for awhile as a simple out-of-the-box option for those who want that. Pipewire has been referred to as Pulseudio 2.0 and apparently works on several distros (from Ubuntu to Arch) with Pulse completely absent and I want that instead. I welcome the day the promise will be realized.

I specified "Current Users" because while 15.0 is still on Pipewire 0.3.70, Current is on 1.0.1, one step up from full release

1 members found this post helpful.

Yep. I'm using pipewire, no problems. You don't want to remove pulse, because a lot is still compiled against it. (pipewire-pulse runs when it's needed, so no troubles there.) In the update something got messed up and I had to redo pipewire-enable.sh, but that wasn't too troublesome.

1 members found this post helpful.

Whomever is referring to pipewire as pulseaudio 2.0 is really doing a disservice to it. It's not being forced upon anyone for one thing or a complete mess under the hood, and the compatible pulseaudio server support is only one part of it.

It's easy to upgrade 15.0's pipewire using the slackbuild from current. See my posts in the other pipewire thread.

2 members found this post helpful.

Thank you, fortysixandtwo. I had forgotten for a moment and misreported that Slackware v 15.0 was on 0.3.70 when in fact it is still on 0.3.44 and some time ago I built 0.3.70 from Current. The last time I tried to go a step further I failed. I will check out your post and try again! Thanks!

1 members found this post helpful.

I really should just submit a slackbuild, but here's the post with the patch and the one about using a newer meson.

https://www.linuxquestions.org/quest...ml#post6453766
https://www.linuxquestions.org/quest...ml#post6457329

2 members found this post helpful.

Just tested, everything works fine.

# pactl info

# wpctl status

^^^^^^^

I'm doing the same. I'll stick with whatever the default is for Slackware.

Thanks for the detailed response. I fully understand.

You asked a question and as a -current user I gave my response the way I see it. I have given thought to switching over to pipewire. There is no guarantee the switch to pipewire will work, though odds are high that it will. I don't record or edit music. I have an aging computer with Creative A60 speakers plugged in to the motherboard jack and USB bluetooth dongle that works. I've decided why mess with it and stick with what Slackware has as default for sound. What would I gain from switching to pulse from what I already have? In my mind, nothing.

I have also problem on latest version Pipewire where bluetooth device does not work

I don't want this thread to turn into a generalization or a rant (much less a generalized rant) so I'll note for anyone like chrisretusn who is very happy with the current state of his PC audio it's utterly obvious there is zero incentive to move to Pipewire. Ultimately our happiness with defaults is all about our workflow and the habits we've developed over decades.

For example, having grown up in computing with DOS shells, like Midnight Commander, and loving most of what IBM's OS/2 prtovided with the (from my POV) horrendous move to Object Oriented Programming (though Rexx was pretty cool) it meant IBM did not include a File Manager. I had to buy one and I did. Now, in 2024, many distros, including apparently Current, are moving away from power permissions and I can only guess why that is.

I'm fairly adept at CLI but if I have a batch of files to manipulate in root space, my default is to "kdesu dolphin", which I've setup with different appearance so I never forget I'm in root, and can choose files, edit, save and move on. I know few people work this way but I truly don't understand why it is simply verboten and not still an option. People with other workflow systems won't ever be aware that option even exists so why shut me out?

Again, I don't want to go off on a tangent but it actually applies here in this thread. If your default patterns of workflow coincide with what's an available option, you will likely be content. If it doesn't, you won't.

IIRC Patrick was "forced" to adopt pulseaudio just like virtually every other distro if for no other reason than the breakage of from Bluetooth support. Briefly he offered a "Pure ALSA" option but understandably that became a royal PITA. Plus, the "just works" aspect pleased casual audio users and some workarounds exist to minimize how much pulse interferes for others. I simply want the option to remove pulse altogether and it appears Pipewire can and maybe will do that.

Much of all this can be laid at the feet of the other Poettering strong arm fiasco, systemd, which by itself is less bad than pulse in my view.. BUT both bullied their way in and I truly don't understand why and how it became so default, and without easy alternative options so fast and so completely.

I don't hate Poettering but I do hate the fork in the road with armed guards essentially cordoning off one of the two that he and his team are largely responsible for affecting all of Linux. I get it why nvidia angered Linus Torvalds so. They made his job harder BUT we and he have options, just buy another brand instead. Yet, the division caused by systemd and pulseaudio has lead to a time that now, does concern Linus deeply, that huge blocks of code like Appimage and whatever other forms of apps with all their requirements included just to "code once, run everywhere" ... well, it's just frustrating.

Again, I will be most appreciative when we have options to suit a wider range of opinions and subjective workflow, and in my case, Audio is hugely important to me. Pipewire looks like it can get there. It's already simplified and streamlined utilizing features common to JACK and vastly reduced latency.

If you're OK with pulse, I'm actually happy for you. If you're not, hopefully something like Pipewire is hopeful.

8 members found this post helpful.