Using Pipewire instead of Pulseaudio in Slackware 15
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,099
Rep:
Quote:
Originally Posted by stormtracknole
Now that Pat has included the daemon package for what will become Slackware 15, I'll note here what is needed in order to use Pipewire instead of Pulseaudio. The original post is here and was provided by ZhaoLin1457. I'm just putting the details of that post here for better visibility........................
I've printed out both of these methods, followed the instructions step-by-step and can't get pipewire to work.
Has there been a change in the procedures?
Thanks.
Last edited by cwizardone; 08-23-2021 at 08:45 AM.
I've printed out both of these methods, followed the instructions step-by-step and can't get pipewire to work.
Has there been a change in the procedures?
Thanks.
Here's my consolidated instructions that I went through the other day to fix up.
Code:
#pipewire setup
-edit /etc/pulse/client.conf to disable pulseaudio
autospawn = no
allow-autospawn-for-root = no #not sure if this is needed but it seems likely
-add the following, this goes with xdg stuff
cat << EOF > /etc/daemon.conf.d/pipewire.conf
pipewire bind,respawn,pidfiles=~/.daemon
pipewire-pulse bind,respawn,pidfiles=~/.daemon
pipewire-media-session bind,respawn,pidfiles=~/.daemon
EOF
-need the following in /etc/xdg/autostart/
#disable pulseaudio
echo "Hidden=true" >> /etc/xdg/autostart/pulseaudio.desktop
cat << EOF > /etc/xdg/autostart/pipewire.desktop
[Desktop Entry]
Version=1.0
Name=PipeWire Media System
Comment=Start the PipeWire Media System
Exec=/usr/bin/daemon -f -n pipewire /usr/bin/pipewire
Terminal=false
Type=Application
X-GNOME-Autostart-Phase=Initialization
X-KDE-autostart-phase=1
EOF
cat << EOF > /etc/xdg/autostart/pipewire-pulse.desktop
[Desktop Entry]
Version=1.0
Name=PipeWire Pulse
Comment=Start the PipeWire Pulse
Exec=/usr/bin/daemon -f -n pipewire-pulse /usr/bin/pipewire-pulse
Terminal=false
Type=Application
X-GNOME-Autostart-Phase=Initialization
X-KDE-autostart-phase=1
EOF
cat << EOF > /etc/xdg/autostart/pipewire-media-session.desktop
[Desktop Entry]
Version=1.0
Name=PipeWire Media Session
Comment=Start the PipeWire Media Session
Exec=/usr/bin/daemon -f -n pipewire-media-session /usr/bin/pipewire-media-session
Terminal=false
Type=Application
X-GNOME-Autostart-Phase=Initialization
X-KDE-autostart-phase=1
EOF
#logout of plasma and startx again or reboot if needed
I've printed out both of these methods, followed the instructions step-by-step and can't get pipewire to work.
Has there been a change in the procedures?
Thanks.
What does not work?
I use with no issues since beginning the "daemon" method of starting the PipeWire daemons from XDG autostart.
Please note that for debugging, you can even execute the commands described on the desktop files on different console tabs, then you can get the messages sent by the PipeWire daemons, which are rather regular programs, with no clues to daemonize themselves.
The proper order of launching their execution is: pipewire, pipewire-media-session, pipewire-pulse
BUT, you should ensure that the PulseAudio server is not (auto-)started.
And of course, you should NOT remove PulseAudio package, because its client libraries and tools are still needed, as usual.
Last edited by LuckyCyborg; 08-23-2021 at 09:12 AM.
I've printed out both of these methods, followed the instructions step-by-step and can't get pipewire to work.
Has there been a change in the procedures?
Thanks.
I recently applied it on my new laptop, and no, obviously it hasn't changed
- The 3 pipewire .desktop files in /etc/xdg/autostart/
- autospawn = no in /etc/pulse/client.conf
And in /etc/xdg/autostart/
- mv pulseaudio.desktop pulseaudio.disabled
I recently applied it on my new laptop, and no, obviously it hasn't changed
- The 3 pipewire .desktop files in /etc/xdg/autostart/
- autospawn = no in /etc/pulse/client.conf
And in /etc/xdg/autostart/
- mv pulseaudio.desktop pulseaudio.disabled
And everything works as expected
Yep!
With the note that I remembered that I read somewhere that XFCE should be configured to load GNOME/KDE services otherwise it's very picky on executing the XDG files - it loads only those with the following
Code:
OnlyShowIn=XFCE;
So, unless the XFCE is configured according, probably we need added on the desktop files at least:
I recently applied it on my new laptop, and no, obviously it hasn't changed
- The 3 pipewire .desktop files in /etc/xdg/autostart/
- autospawn = no in /etc/pulse/client.conf
in /etc/xdg/autostart/
- mv pulseaudio.desktop pulseaudio.disabled
And everything works as expected
FYI pulseaudio.desktop will get reinstalled by the pulseaudo-15 package.
Who is "we"? You may know, but I didn't see it stated clearly in this pipewire setup thread or the original.
Who is "we" ? Anybody who used on having interest on running PipeWire as audio-server.
Is obvious that that PulseAudio file for XDG autostart would be reinstalled on package upgrade, even is not stated "clearly" if you have a vague idea what PulseAudio package contains.
Who is "we" ? Anybody who used on having interest on running PipeWire as audio-server.
Is obvious that that PulseAudio file for XDG autostart would be reinstalled on package upgrade, even is not stated "clearly" if you have a vague idea what PulseAudio package contains.
Maybe those files could be considered as config files and so we could apply the ".new" stuff as is done for a lot of config files.
Personally, regarding pulseaudio.desktop file, I just copied /etc/xdg/autostart/pulseaudio.desktop to ~/.config/autostart/pulseaudio.desktop then added "Hidden=true" to it. That way, I don't have to remember editing /etc/xdg/autostart/pulseaudio.desktop after upgrading the pulseaudio package. Seems to be working so far for a couple of months here on my system.
Maybe those files could be considered as config files and so we could apply the ".new" stuff as is done for a lot of config files.
How we can do this? To use the PipeWire as audio server, you should disable the PulseAudio server auto-start - and this means also to move away the file /etc/xdg/autostart/pulseaudio.desktop so nothing is on place of it.
Like I said many times, probably the best way is to have the PulseAudio server (and its related files) put in a split package, which can be eventually uninstalled or blacklisted.
This is more a "slackware" thing than a specific pipewire/pulseaudio one
It is specific to someone using pipewire on slackware and why we are in this thread. It is also an easy detail to overlook/forget about when updating the system until/if it's a default option.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
