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.

1 members found this post helpful.

Interesting, I couldn't get pipewire to work in XFCE without using that in the desktop file.

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

Then, maybe you should look on how XFCE handle those XDG autostart files. Could be even a (new) bug.

I am quite sure that, months ago, I had no issues to start the PipeWire daemons on XFCE with those stock XDG autostart files.

1 members found this post helpful.

When I first tested this, I did so under KDE. So I can't say for sure if this was working at any point with XFCE.

Well, I can confirm you that it works fine even today - with the stock XDG autostart files. I've just tested on full updated system.

Attached Thumbnails

 

2 members found this post helpful.

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.

1 members found this post helpful.

Well...I need to look at my set up again. I obviously missed something on that system. Thanks for checking your system.

LuckyCybord,

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.

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.

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
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

https://docs.xfce.org/xfce/xfce4-session/preferences

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.

1 members found this post helpful.

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.)

ETA: I'm not using wayland. Just X.

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

2 members found this post helpful.