Announcement

Collapse
No announcement yet.

KDE Plasma Working On Wayland Screen-Sharing With XDG-Desktop-Portal / Pipewire

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • KDE Plasma Working On Wayland Screen-Sharing With XDG-Desktop-Portal / Pipewire

    Phoronix: KDE Plasma Working On Wayland Screen-Sharing With XDG-Desktop-Portal / Pipewire

    With Wayland not enforcing any standard for screensharing, KDE developers are now building off GNOME's approach of XDG-Desktop-Portal and PipeWire for desktop/screen sharing for adding this feature to Plasma on Wayland...

    http://www.phoronix.com/scan.php?pag...d-Screen-Share

  • #2
    Ok, so something does not compute here, could someone who understands this stuff please explain.

    - This is based on something from Gnome
    - It involves sending GBM buffers
    - Gnome has patches to support EGL streams because Nvidia are tools

    Does this mean that
    - Gnome supports EGL streams, but not for screen sharing
    - The fact that this uses GBM buffers is irrelevant and will still work on the EGL stream implementation that Gnome has
    - I'm an idiot and have got my facts horribly wrong

    Comment


    • #3
      There is lots of parts of the Wayland ecosystem that Nvidia doesn't support properly, which is part of the reason that Martin refuses to consider EGLstreams because so many other systems don't work right. So I think it is the first case?

      Screen sharing is one of the last big issues for Wayland, imo

      Comment


      • #4
        - Gnome supports EGL streams, but not for screen sharing
        Correct, they use glReadPixels, i.e. copying.

        - The fact that this uses GBM buffers is irrelevant and will still work on the EGL stream implementation that Gnome has
        No, it won't work. GBM is used to pass buffer in video memory from one application to another. EGL Streams requires different approach.

        - I'm an idiot and have got my facts horribly wrong
        No (:

        Comment


        • #5
          The fact that in Wayland-land there is no standard for network transparency leaving it to window-manager specific and possibly not fully interoperable implementations is a sad state of things. It appears to leave Linux way behind not just Windows, but also behind yesterday Linux itself where Xorg and Xpra enabled both desktop level and application level operation over the network for any application and window manager.

          Comment


          • #6
            Originally posted by callegar View Post
            The fact that in Wayland-land there is no standard for network transparency leaving it to window-manager specific and possibly not fully interoperable implementations is a sad state of things. It appears to leave Linux way behind not just Windows, but also behind yesterday Linux itself where Xorg and Xpra enabled both desktop level and application level operation over the network for any application and window manager.
            It's not like they've been caught off guard here, they knew it would require work because Wayland has been designed to be secure from the ground up. This causes issues for things which require global access/data such as screen sharing, but has massive benefits when you don't want a keylogger on your system. Nobody is saying Wayland has feature parity with Xorg, there's a few last things to sort out, but they're working on it, this article is testament to that.

            Comment


            • #7
              Originally posted by callegar View Post
              The fact that in Wayland-land there is no standard for network transparency leaving it to window-manager specific and possibly not fully interoperable implementations is a sad state of things. It appears to leave Linux way behind not just Windows, but also behind yesterday Linux itself where Xorg and Xpra enabled both desktop level and application level operation over the network for any application and window manager.
              Really this is missing the elephant in the room. X11 and Xpra remote desktop was becoming more and more non functional as more and more applications used opengl so its has not been any application and windows manager over X11 remote desktop for years it been selected applications and applications with features disabled. So a new method had to be designed. Yes this new method provides a clean way to revoke the connection neither Xpra or Xorg ever provide that.

              So far gnome and kde are unified around the same interface for doing it.

              Comment


              • #8
                What protocol PipeWare use for transferring data? VNC or Spice?

                Comment


                • #9
                  Originally posted by RussianNeuroMancer View Post
                  What protocol PipeWare use for transferring data? VNC or Spice?
                  Technically pipewire does not support a remote desktop protocol at all and the role here it really never has to. Its a local protocol to get data from the protect screen and audio to application to perform remote desktop protocol using a method that can be revoked on the fly.

                  https://wiki.gnome.org/Projects/Mutter/RemoteDesktop

                  What Pipewire does sets up the transport and perform the transport. Under gnome they are working on gnome-remote-desktop that hooks on the end of this stack and provide a very unprotected vnc at the moment.

                  Of course you could have chrome with its remote desktop hooking on to the pipewire transport as well. If all the tools are using the same framework the gnome tools should be use-able with KDE and the kde tools should be usable with gnome for remote desktop.

                  Personally I would like to see a deeper option being a KMS driver for remote desktop so compositors/x11 server don't need to know about it for desktops that are actively shared.

                  Really we have need a new standard for doing remote desktop for quite some time particularly for the temporary access cases and to prevent some random application starting a full remote desktop without user permission.

                  Comment


                  • #10
                    Originally posted by RussianNeuroMancer View Post
                    What protocol PipeWare use for transferring data? VNC or Spice?
                    Call it hype, but I'd love to see the Wayland standardized remote desktop protocol use AV1 streaming as its transport. RFB nowadays is a horribly inefficient protocol compared to what mp4 and hls streams have demonstrated is possible. Maybe SPICE can be amended for it since AV1 alone doesn't provide IO signaling.

                    Comment

                    Working...
                    X