- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
Changelog:
Rewritten with Flutter
Support ipv6 (beta)
Strengthed password
Quick support feature
Hardware codecs H264 / H265 (beta)
AV1 codec
International keyboard (Map mode and translate mode)
Wayland support (beta, known issues #4276 (comment))
Privacy mode (beta, Windows only)
Headless Linux
Virtual display (Windows)
Resolution adjustment
Dark theme
A lot of improvements (#918)
https://rustdesk.com / https://github.com/rustdesk/rustdesk/
You must log in or register to comment.
Wayland support, would you look at that!
Was it rustdesk or some other popular open source remote desktop software that had “no plans of supporting wayland”? In any case, nice!
Just a beta feature though. Last time I checked it still didn’t work unattended. So unless the missing wayland puzzle pieces are in place now, it’s likely still unusable for be.
Edit: nice, with the
--servicemode running, I can at least connect just fine to my running Gnome session and actually see something and can control the input. But if the session is locked, it’s not possible yet. So it looks like we are slowly getting there.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.
Used to use TeamViewer as I supported it for a company and was familiar with it but I got tired of the 2 hour session limit. Found Rustdesk through some Google searching and now I run my own install of it. Absolutely love it for my use case and I’m glad they’re able to keep putting out updates!
Do they have a flatpak yet?
https://github.com/rustdesk/rustdesk/wiki/Run-flatpak
https://github.com/rustdesk/rustdesk/releases/tag/1.2.0 -> rustdesk-1.2.0-x86_64.flatpak
Always cool to see it progress!
Rewritten with Flutter
Wasn’t it from the start?
I am not sure myself, so the following may be wrong.
In my understanding, the rewrite refers to the RustDesk desktop whose interface appears to have been created with Sciter, which was replaced by Flutter.
what is hesdless linux?
Like a server with no direct input output accessibility. X can be run remotely.
One more version without the obvious UPnP. At this point I think they’re not implementing UPnP in order to somehow profit from the lack of it in the future. Who on their right minds wants all traffic going over a server when in most cases you can simply use UPnP? This makes no sense.
Also yet another version with the address book not implemented, but I bet the sign in button is still on the client to continue to confuse new users. Almost 2 years that button has been there to do nothing.
