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.
xdg-desktop-portal would be a much welcomed addition for us non KDE wayland users
Well, the addition of xdg-desktop-portal will solve certainly the stack for Plasma5, because there's already xdg-desktop-portal-kde
In practice, when an application wants to do screen recording on Wayland/Plasma5, the things works like this:
- the application asks xdg-desktop-portal for a video stream for screen recording
- the xdg-desktop-portal looks for a frontend, and finds running xdg-desktop-portal-kde, so asks it for the video stream
- the xdg-desktop-portal-kde show to user a confirmation dialog (if accepts or not) then asks KWin for the video stream.
- the Kwin setups a new PipeWire video stream and sends the handle to xdg-desktop-portal-kde
- the xdg-desktop-portal-kde sends the handle of video stream (and that information that the user accepted) to xdg-desktop-portal
- the xdg-desktop-portal sends the handle of video stream to application, which then do its job.
All communication is done via DBUS.
Even sounds complicated, this logic ensure that the applications talks always with xdg-desktop-portal no matter which desktop session and implementation runs on the desktop.
So, those who uses different desktop session on Wayland - non Plasma5, will need to run also particular implementations, like xdg-desktop-portal-wlr for WLROOTS based DEs or xdg-desktop-portal-gtk for Wayland/Gnome3.
Last edited by LuckyCyborg; 07-06-2021 at 01:57 PM.
Thanks @LuckyCyborg This is very interesting. Yes, -wlr is the drone I'm looking for. While I compiled and installed it manually I have virtually no idea how to properly set it up.
But I suppose we're getting off topic
Thanks @LuckyCyborg This is very interesting. Yes, -wlr is the drone I'm looking for. While I compiled and installed it manually I have virtually no idea how to properly set it up.
But I suppose we're getting off topic
I have no idea how to setup xdg-desktop-portal-wlr on Slackware and your particular Wayland DE, BUT I am 100% certain that also xdg-desktop-portal is required.
Do you mind sharing one of your pipewire desktop files here? Just want to make sure I am not missing something. Thanks!
Considering that he's the inventor of those XDG desktop files, probably he uses exactly the files described on this thread's first post.
Also myself I use them and if you want a second confirmation, I would like to inform you that the PipeWire daemons runs properly on XFCE also on my mini-PC MinisForum Z83-F.
I've tested this after upgrading to "Tue Jul 6 20:44:20 UTC 2021" updates.
Last edited by ZhaoLin1457; 07-07-2021 at 05:46 AM.
Considering that he's the inventor of those XDG desktop files, probably he uses exactly the files described on this thread's first post.
Also myself I use them and if you want a second confirmation, I would like to inform you that the PipeWire daemons runs properly on XFCE also on my mini-PC MinisForum Z83-F.
I've tested this after upgrading to "Tue Jul 6 20:44:20 UTC 2021" updates.
Thanks ZhaoLin. This does help. I'm just perplexed as to why this wasn't working on this particular system. No big deal though. Thanks for chiming in.
Do you mind sharing one of your pipewire desktop files here? Just want to make sure I am not missing something. Thanks!
As @ZhaoLin1457 already supposed, I use exactly the XDG autostart files described on this thread. There's one, for the sake of fulfilling your request.
/etc/xdg/autostart/pipewire.desktop
Code:
[Desktop Entry]
Version=1.0
Name=PipeWire Media System
Comment=Start the PipeWire Media System
Exec=/usr/bin/daemon -frB --pidfiles=~/.run --name=pipewire /usr/bin/pipewire
Terminal=false
Type=Application
X-GNOME-Autostart-Phase=Initialization
X-KDE-autostart-phase=1
Honestly, I believe that your issues are in fact related to how you configured your XFCE - how about to start the XFCE on a new created user, with its default options?
I for one, I suspect that you modified the options of starting services on xfce4-session
Let's say that you disabled both the startup of Gnome and KDE services for whatever reasons, because looks like that the XFCE uses "OnlyShowIn" to identify its own services on XDG autostart.
Last edited by LuckyCyborg; 07-07-2021 at 11:17 AM.
As @ZhaoLin1457 already supposed, I use exactly the XDG autostart files described on this thread. There's one, for the sake of fulfilling your request.
/etc/xdg/autostart/pipewire.desktop
Code:
[Desktop Entry]
Version=1.0
Name=PipeWire Media System
Comment=Start the PipeWire Media System
Exec=/usr/bin/daemon -frB --pidfiles=~/.run --name=pipewire /usr/bin/pipewire
Terminal=false
Type=Application
X-GNOME-Autostart-Phase=Initialization
X-KDE-autostart-phase=1
Honestly, I believe that your issues are in fact related to how you configured your XFCE - how about to start the XFCE on a new created user, with its default options?
I for one, I suspect that you modified the options of starting services on xfce4-session
Let's say that you disabled both the startup of Gnome and KDE services for whatever reasons, because looks like that the XFCE uses "OnlyShowIn" to identify its own services on XDG autostart.
I think you are on to something. This particular account that I am using is old and has seen many instances of xfce. I obviously have something messed up there. I probably should have looked more into that before I chimed here. Thank for your tips.
Another data point, but XFCE, pipewire, and SuperCollider started right up. Latency was kind of ass, but I haven't really tuned my laptop for latency. (That is, just default jackdrc, no kernel params yet.)
I tried out Pipewire on one of my Test Current installs and thought it might have shown me a way to simplify and improve ALSA interaction with JACK in a Pulse environment. turned out to not work. I suppose it was likely just a case of Premature Jack Elation
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.