On Monday, June 3, 2019 5:21 PM, <[email protected]> wrote: > > xdg-desktop-portal should probably be used for this. The internal > > > compositor-specific D-Bus interfaces are not meant to be used by > > third-parties AFAIK. > > I looked into xdg-desktop-portal but AFAIK it doesn't provide a real > RDP API (e.g. it user-prompts for devices or screens choice and has > no way to do that in the background as a real RDP server daemon would > require). That's why I was considering the internal interfaces.
That's true. Maybe this issue should be raised on the xdg-desktop-portal issue tracker. > I still don't understand: if I have two users connected to their > respective gnome-shell (or plasma shells) implementing Wayland, how > do I tell one process launched by perhaps a third user to capture one > user's instead of the other's desktop? Two users would have a different D-Bus session bus. A third user wouldn't be able to capture someone else's desktop. > > Il 3 giugno 2019 alle 13.55 Simon Ser [email protected] ha scritto: > > On Monday, June 3, 2019 1:24 PM, [email protected] wrote: > > > > > My goal would be to capture screen data for an entire desktop session > > > (either KDE or GNOME). I know that compositors like mutter provide > > > internal d-bus interfaces to get this kind of data and enable RDP > > > operations […] > > > > xdg-desktop-portal should probably be used for this. The internal > > compositor-specific D-Bus interfaces are not meant to be used by > > third-parties AFAIK. > > > > wayland-devel mailing list > > [email protected] > > https://lists.freedesktop.org/mailman/listinfo/wayland-devel _______________________________________________ wayland-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/wayland-devel
