149
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 07 Jul 2023
149 points (100.0% liked)
Linux
48186 readers
1070 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
That is also a wayland showstopper for me personally. Does someone know if it is a per se wayland issue or is there "only" the implementation missing (i.e. in plasma wayland for instance)?
Wayland is all about protocols being implemented by the DEs. So far there is (afaik) not a fitting protocol for remote desktop usecases.
Even screensharing is still a PITA, since the desktop portals work independantly from the requesting application. App asks portal "what apps and screens are there?", then the user gets prompted by the portal to select the allowed entities. Then the application lists these again, user picks it again, and then gets prompted by the portal again to basically confirm that you really want to share it. That's mostly a discrepency between how the apps work (on X11, Windows and OSX vs Wayland). But it's in the end still a pain for the user.
Grabbing and manipulating inputs is another matter. Allowing that globally is a security issue, so Wayland doesn't do it. But remote desktop needs that. So now there needs to be a standard protocol that the DEs implement to allow remote desktop solutions to access inputs. Or they do it like RustDesk, run as root and intercept inputs before wayland gets a chance to intervene.
Thanks for the insights. Than I might try RustDesk again, and see if they successfully worked around the wayland shortcomings.
Yeah, screensharing is not optimally either, but at least it is working. I mean I could live with a portal which operates like for example a file chooser, but than it should implement the whole process of choosing a window or a screen without any further interaction necesary in the parent application.