Release 1.2.0 · rustdesk/rustdesk
github.com
Winget, FDroid, Apple Sillicon, Google Play / App Store update will come soon. x86-64: Windows | Ubuntu | Mac AArch64 (ARM64): Ubuntu | Android More: check below please Changelog Rewritten with...

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/

  • solariplex@slrpnk.netEnglish
    5·
    1 year ago

    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!

    • aksdb@feddit.deEnglish
      1·
      1 year ago

      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 --service mode 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.

      • RasenEmu@feddit.deEnglish
        0·
        1 year ago

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

        • aksdb@feddit.deEnglish
          2·
          1 year ago

          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.