With the new release of GNOME Remote Desktop, sessions are now persistent. It’s the only Wayland solution that offers easy RDP access for remote users, and I’d say it actually beats the X solutions right now. At least for my use case.
I haven’t yet upgraded my server to test out the new release, though some have already. So that’s an option for users who want this, though it only works with GNOME.
I just tested this today and I was surprised to discover that RDP on plasma-wayland systems now works great, even on a plasma-nvidia-wayland host.
Also pleasantly surprised that the RDP client shows both connected displays on the host machine. In addition, RDP is stable even when connecting from a client over a wireless / cellular interface. It also works for a non-3389 port at the host.
Thank you KDE devs for the excellent work !
Here’s a sample setup, if anyone wants to try again :
Wayland Host
Wayland Client
On a side note, the KRDP github page is missing KRDC as a working client, which probably should be added.
I was sent here as a better place to ask than the Aurora board. I don’t know Aurora or Fedora but set it up on an old Surface because it worked and most didn’t.
I have a small but nagging problem. I wanted it set up as an in-house “kiosk” for my Home Assistant. It boots, auto-logins, runs Firefox and shows my dashboard. It works great.
Except… with that tiny display when i want to work on something I want to RDP in, and now that i set it up for auto-login I cannot figure out how to make it work. It worked great before I did that.
The RDP screen requires a user name. I assume (but am not sure) that is a separate username than linux. I set up “rdp” and password “rdp” there, but I get “The token supplied to the function is invalid” from Windows RDP client.
In the log is:
Feb 26 11:34:02 aurora.xxxxxxx xdg-desktop-portal-kde[2211]: xdp-kde-remotedesktop: MegaAuth: Failed to lookup permissions: "No entry for remote-desktop"
I have tried using the linux account there but it requires a password, so that won’t work (it worked before just fine, when it had a password, I used the same as linux).
Is the lack of a password on the logged-in linux account causing this error, or have I broken something else?
Linwood
RDP is literally the sole reason I’m still using x11. This would be game changing.
How did you install it? Did you build it yourself?
The RDP username and password is different than the Linux login password. If you go to System Settings → Remote Desktop you should setup the user name and password that you want to use, and then - after that user logged in, even automatically, you should be able to RDP in and use the user name and password you have set up.
Thank you @guss77, and apologies for being dense but unsure of “that user”…
Let’s say my logged in user on the console is ABC. User ABC is in linux with no password and auto-logged in.
Does the RDP username entered on the setup page have to be ABC, or can it be XYZ?
Here is the issue – I cannot make it ABC with no password because the screen requires a password. If I enter ABC on the RDP setup with a made-up password (thus not matching linux’s no password) it fails.
If I enter XYZ with a password, and use that from the RDP client, it fails.
I do not know if these combinations are failing because of lack of using the same username/password in the RDP setup as in linux, or failing simply because the logged in user has no password, but no combination appears to work.
Dead end, or am I missing something?
Note that this works fine if I restore the password to ABC, and use ABC with the proper linux password on the RDP setup screen. But I want auto-login (on the console, not RDP) and that appears to require no password.
That is an interesting observation.
On my system I can set up RDP users in my Linux user’s System Settings and they work just fine, but I don’t use auto-login or passwordless accounts. I have another system where I use auto-login with also a password (that is only used for remote login and for sudo) so I should try that configuration and see how that works.
But at this point this seems like a bug that is worth reporting on bugs.kde.org.
This is interesting and frustrating. It’s something of a mess.
First, i was simply wrong, I assumed you had to remove the password to auto-login (some distro’s you do apparently). So I was able to put the password back on to the underlying auto-login linux account.
Having done that I thought I would be good in terms of the overall process, I cleared the dummy account and put the same account name (still unclear if it connected) as the remote desk user with the same passsword.
Preseto… didn’t work. Hmm… RDP not running. Enable. Reboot, didn’t work… it’s not enabled again. Enable, RDP – worked. Reboot – not running. Double check it’s set to restart on reboot.
It may be related to this, though I don’t know what it means:
Mar 04 11:56:32 aurora.leferguson.com krdpserver[2752]: qt.dbus.integration: QDBusConnection: error: could not send message to service "org.freedesktop.portal.Desktop" path "/org/freedesktop/portal/desktop" interface "org.freedesktop.portal.RemoteDesktop" member "NotifyKeyboardKeycode": Marshalling failed: Invalid object path passed in arguments
So turned off auto-login (leaving the password), turned on RDP, rebooted (so at this point with password, with RDP enabled, without auto-login, so basically defaults):
Now RDP won’t restart. When I log into the attached monitor it’s disabled. Enabled, changed the slider a bit (to make sure the apply button would come up just in case), applied. Rebooted…
Disabled again.
Still getting that error above. So it’s now apparently just broken, but in a different way.
I think this is just… immature. And messed up.
Thank you for trying to help.
The RDP service in Plasma is definitely not mature - its a brand new implementation that didn’t get enough love yet, and there’s a lot more stuff to do.
If you’re interested in helping out, I can come up with some troubleshooting steps that we can try, to nail down the problem of why the RDP service won’t auto start for you.
Delighted to help debug. I’m always hesitant to post bugs or PR’s on git, as usually there’s a bazillion artificial hurdles to jump over to reduce the flow, but testing is easy.
I should reiterate this is a vintage 2012 or so Surface Pro (original, no number), so the hardware could be an issue also.
Mine stopped starting as well with a recent update. I just created a simple script adding a 3 sec delay before running krdpserver and start it as a loginscript
Interesting. I suspect aurora auto-updates, so it could be that and not something I did.
I installed the package from the Manjaro extra repo : pamac install krdp