Grd (Gnome remote desktop) features (or lack therof) and roadmap?

At my university, I currently run a linux terminal server which provides remote linux (Xfce) desktops to the Windows PC’s of our students and faculty using xrdp. We are very happy with xrdp and its features, but it is X only, no way to move to wayland at all.

I’m investigating ways to switch to wayland, and I try to get an idea if switching to wayland will be possible now, in some months, or in some years at best.

Of all wayland RDP solutions, Grd is closest to what we need.
As far as I can tell from the documentation, Grd supports

  • Multiple virtual remote desktops with no physical screen (headless).
  • PAM-based user authentication.
  • Session management with separate per-user sessions.
  • Persistent sessions (users can disconnect and reconnect).

Is that correct?

However, I was not able to verify the following features (which xrdp offers and which we depend on) from Grd’s documentation:

  1. Does Grd+Gdm fully support non-Gnome desktops (Xfce, KDE, …)?
  2. Does Grd require graphics/video hardware on the server side (and share it between all users / sessions), or will it also work with software rendering (and software video codecs) only (no graphics HW in the server)?
  3. Does Grd support two-way clipboard sharing (copy & paste) between the client (Microsoft Windows RDP client) and the wayland session? Only text or also files?
  4. Does Grd support client local drive sharing with Microsoft Windows RDP clients in the same way as xrdp does? (using their RDP connection, remote users can access the local drives, USB sticks etc. of their Windows clients as subdirectories in their homedir on the linux server: The client’s drives are automatically mounted as fuse filesystems with correct ownership and protection on the server).
  5. Are national charsets and national keyboard layouts on the Windows clients handled correctly?

What is already working in Grd? What is planned? When?
What will not be supported in the forseeable future?

It currently only works with GNOME prefixed APIs.

It does not require hardware acceleration, and works with software rendering, be it in the display server, or gnome-remote-desktop.

Clipboard sharing works. It also supports clipboard file sharing via a fuse filesystem.

Local drive sharing is not implemented.

The keyboard layout is handled compositor side, with the RDP client sending what roughly corresponds to evdev keycodes. These keycodes gets translated using whatever keyboard layout is active in GNOME, which means anything that GNOME supports, be it Latin based, CJK, etc.

There is no official roadmap, and what gets implemented depends on available contributor time which is hard to predict.

1 Like

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.