As described. I wish the RDP will show the GDM on Wayland and I can launch, for example, sway, via Wayland from a remote device.
There is some misunderstanding. Wayland is the local only protocol which does not include networking. It is possible to access existing remote Wayland compositor using something else, e.g. RDP, as long as this compositor supports it (screen sharing). It is also possible to have headless compositor (without real devices) which is similar to Xvnc. The former should be possible for quite some time - remote access to the existing local session. The latter is rumored to be supported in GNOME including authentication similar to X11 display manager, not sure about KDE. Last time I checked Tumbleweed missed the prerequisite version of FreeRDP, I have not looked recently.
By design only Wayland compositor has full access to the screen content, so you need to check whether it is supported. It is supported by GNOME and KDE native compositors. Quick search shows examples of running sway with wayvnc in headless mode.
https://wiki.gnome.org/Initiatives/Wayland/Remoting
https://wiki.gnome.org/Projects/Mutter/RemoteDesktop
https://software.opensuse.org/package/gnome-remote-desktop
For KDE:
Well … the problem is client 
I briefly tested it on Tumbleweed KDE - server part works and I can connect, but I need RDP client with video streaming support, otherwise …
krdpserver[4267]: org.kde.krdp: Client does not support H.264 in YUV420 mode!
and neither Remmina nor freerdp3 Linux clients here work. I do not have Windows clients to test.
Without actually trying it (for the lack of a suitable client) settings look rather different:
That is different from the ability to authenticate remotely as an arbitrary user.
AFAIU KDE wants hardware H.264 support. For Mesa 3D that means using VA API drivers (Mesa-libva) from Packman or opi.
May be. I can connect to GNOME Wayland session in desktop sharing mode so H.264 problem seems to be KDE specific. I am still unable to configure remote login in GNOME, it fails with different D-Bus errors.
One error is related to TPM2 support and is not fatal (could be additional configuration issue or bug). Another error is related to certificate management, when enabling remote login via settings application it fails to configure certificate. Maybe some additional service is missing.
When configured manually, remote login works. I get the standard GDM greeter screen and can login. I also have to pre-authenticate using user/password set for gnome-remote-desktop, but it only gives access to GDM. When logged in, GNOME also shows indication that this session is remote. I also was able to login on the local console as a different user. What is apparently not possible - the second remote session or remote session when local one is already active. GDM greeter simply fails (or refuses) to start.
bor@tw:~> grdctl --system status
Failed to create connection with service: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Sender is not authorized to send message.
Init TPM credentials failed because Failed to initialize transmission interface context: tcti:IO failure, using GKeyFile as fallback.
Overall:
Unit status: active
RDP:
Status: enabled
Port: 3389
TLS certificate: /var/lib/gnome-remote-desktop/rdp-tls.crt
TLS fingerprint: 70:52:22:42:79:c1:d9:6f:bf:23:7c:f7:ee:6b:6c:1c:a9:1b:ff:f0:11:e5:8e:d9:65:ba:48:53:59:5f:13:a9
TLS key: /var/lib/gnome-remote-desktop/rdp-tls.key
Username: (hidden)
Password: (hidden)
bor@tw:~>
bor@tw:~> loginctl
SESSION UID USER SEAT LEADER CLASS TTY IDLE SINCE
10 1002 testuser seat0 5404 user tty2 no -
11 1002 testuser - 5433 manager - no -
6 459 gdm - 3495 manager-early - no -
7 1001 bor - 4325 user - no -
8 1001 bor - 4347 manager - no -
c5 459 gdm seat0 3485 greeter tty7 no -
6 sessions listed.
bor@tw:~>
So, remote login works to some extent in the current GNOME stack. You can login remotely when nobody is active locally. I have no idea whether it is by design or something is still missing.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.