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.
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.
Obvious if you remember, but very easy to overlook and forget about and anybody new to trying out pipewire on slackware needs to be aware of even if it's just a reminder until pipewire "is" a default configurable option.
Your use of "we" is very contradictory in this case. Remember that not everyone lives and breathes this stuff to the same level/intensity that you appear to do.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Rep:
Quote:
Originally Posted by fourtysixandtwo
Obvious if you remember, but very easy to overlook and forget about and anybody new to trying out pipewire on slackware needs to be aware of even if it's just a reminder until pipewire "is" a default configurable option.
Your use of "we" is very contradictory in this case. Remember that not everyone lives and breathes this stuff to the same level/intensity that you appear to do.
That maybe my problem.
I spent a couple hours two weeks ago working on this project, another two or three hours again yesterday and all this morning today and pipewire does not work. There must be something so fundamental that it is obvious to others with more knowledge and experience, but I don't see it.
Are they there any dependencies that are not included with -current?
That maybe my problem.
I spent a couple hours two weeks ago working on this project, another two or three hours again yesterday and all this morning today and pipewire does not work. There must be something so fundamental that it is obvious to others with more knowledge and experience, but I don't see it.
Are they there any dependencies that are not included with -current?
The PipeWire "daemons" are just ordinary programs, which has no ideas regarding PID files and other daemon-like things. They do not put PID files anywhere.
The one which puts PID files there is our daemon supervisor - the little program which controls the PipeWire "daemons" and executes/stops them as instructed.
However, even for the daemon supervisor those PipeWire daemons are just ordinary programs too and it has nothing to do with PipeWire itself.
It's a generic daemon supervisor, capable to supervise things even on init system - in fact for this purpose it was created years ago.
For example, I have a friend who uses the daemon supervisor to automatically start and stop a VPN client executed on user side.
Last edited by LuckyCyborg; 08-23-2021 at 03:23 PM.
Great Wizard, the biggest question is: what desktop environment you use?
And IF you use the solution described on OP of this thread and the XFCE as I suspect, did you read my comments regarding XFCE and running its desktop services?
Last edited by LuckyCyborg; 08-23-2021 at 04:41 PM.
That maybe my problem.
I spent a couple hours two weeks ago working on this project, another two or three hours again yesterday and all this morning today and pipewire does not work. There must be something so fundamental that it is obvious to others with more knowledge and experience, but I don't see it.
Are they there any dependencies that are not included with -current?
I just set it up on another -current machine without issue.
You should see the following processes and files in ~/.daemon or ~/.run (depending on pidfile location specified)
Code:
# ps -eaf|egrep "pipew|pulse|jack"
test 3337 1 0 15:14 ? 00:00:00 /usr/bin/daemon -f -n pipewire-pulse /usr/bin/pipewire-pulse
test 3340 3337 0 15:14 ? 00:00:00 pipewire-pulse: /usr/bin/pipewire-pulse
test 3341 1 0 15:14 ? 00:00:00 /usr/bin/daemon -f -n pipewire /usr/bin/pipewire
test 3345 3341 0 15:14 ? 00:00:00 pipewire: /usr/bin/pipewire
test 3352 1 0 15:14 ? 00:00:00 /usr/bin/daemon -f -n pipewire-media-session /usr/bin/pipewire-media-session
test 3357 3352 0 15:14 ? 00:00:00 pipewire-media-session: /usr/bin/pipewire-media-session
root 3466 1347 0 15:16 pts/0 00:00:00 grep -E pipew|pulse|jack
# ls -l ~test/.daemon/
total 24
-rw-r--r-- 1 test users 5 Aug 23 15:14 pipewire-media-session.clientpid
-rw-r--r-- 1 test users 5 Aug 23 15:14 pipewire-media-session.pid
-rw-r--r-- 1 test users 5 Aug 23 15:14 pipewire-pulse.clientpid
-rw-r--r-- 1 test users 5 Aug 23 15:14 pipewire-pulse.pid
-rw-r--r-- 1 test users 5 Aug 23 15:14 pipewire.clientpid
-rw-r--r-- 1 test users 5 Aug 23 15:14 pipewire.pid
On my main desktop, which is using digital out, I may have had to configure that output from the Audio control panel again.
Does your audio work without pipewire configured? I had to reinstall alsa-lib and pulseaudio-15 after a recent update (if you haven't been following that recent audio not working thread).
Neither directory exists on this system.
Pulseaudio works just fine.
That will happen if pidfiles isn't specified in either the /etc/daemon.conf.d/pipewire.conf from my example or the "Exec" line in the pipewire*.desktop files from the OG post of this thread. I still got sound but daemon is unable to kill the processes after logging out from that shell.
You did see the 6 daemon/pipewire processes running?
Last edited by fourtysixandtwo; 08-23-2021 at 05:43 PM.
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.
So far i have not been able to figure out the problem when i start Cinnamon it takes about 15s to load, this does not happen in other environments such as XFCE or Enlightenment.
And this only started after using these .desktop on XDG / Autostart
Looked into that, but couldn't find anything definitive on the matter.
Perhaps, some interesting points. not about audio, but ...
Code:
We use xdg-desktop-portal (+ backend implementation) for communication between the app requesting
to share a screen and between desktop (Plasma or Gnome). You need xdg-desktop-portal, which is the
middle man between the app and backend implementation, compiled with screencast portal.
Code:
For backend implementation, if you are using Plasma, you need xdg-desktop-portal-kde from Plasma 5.13.x,
again compiled with screencast portal, which is build when PipeWire is present.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
