So currently Wayland doesn't work at all for the controlled host and based on your reply will never work?

Yes, but should not never work

The transaction from X11 to Wayland is the pain for sure, Wayland will take part of the Linux Desktop in the future.

This is the upstream issues, we should hope Wayland implement macOS or Flatpak like permission control, in that case, user will not need to authorise the permission over and over again, but in certain aspects, this is violates the Wayland goal, but let them fight on the freedesktop. org mailing list or GitLab.......

But should it work on hosts for which I have attendance? Because that didn't work for me as well. I tried to connect from a macOS host to a Linux host but didn't get around that dialog.

No matter how the software requires, the Screen Capture permission on Wayland should lost after reboot, but I can't sure what is going on in your case, it is kinda security flaws by design.

@rustdesk, I don't know if this is a true limitation of Wayland per-se. At least I can successfully use Sunshine(host)+Moonlight(client) without having to confirm any dialogs whatsoever (after the pairing with the PIN). Maybe the Rustdesk team can investigate Sunshine and find whatever black magic it's using and copy that.

Thank you in advance!

Instructions for above:

gnome-remote-desktop "Desktop Sharing"

as root:

dnf -y install gnome-remote-desktop freerdp
firewall-cmd --permanent --add-service=rdp
firewall-cmd --reload
firewall-cmd --list-all

stop system ("remote login") service if running (as root):

systemctl stop gnome-remote-desktop.service

as desktop user:

RDP_USER="rdptestuser"
RDP_PASS="12345678"
mkdir -p ~/.local/share/gnome-remote-desktop
winpr-makecert -silent -rdp -y 2 -path ~/.local/share/gnome-remote-desktop/certificates rdp-tls
grdctl rdp enable
grdctl rdp disable-view-only
grdctl rdp set-credentials "${RDP_USER}" "${RDP_PASS}"
grdctl rdp set-tls-key ~/.local/share/gnome-remote-desktop/certificates/rdp-tls.key
grdctl rdp set-tls-cert ~/.local/share/gnome-remote-desktop/certificates/rdp-tls.crt
grdctl status --show-credentials
systemctl --user --now enable gnome-remote-desktop.service
systemctl --user status gnome-remote-desktop.service

Everything shown above can be done locally or via SSH from an external host.

clients

linux

sudo dnf -y install gnome-connections
gnome-connections rdp://host

windows

mstsc

The RDP clients (gnome-connections or mstsc or whatever) will log in with the credentials provided in RDP_USER & RDP_PASS, and no wayland popup dialog appears on the desktop ... the connection proceeds without interference.

RDP support on DE itself is completely different things

And yes, I can now make GNOME 47 and latest KDE 6 remember the permission, but it should take a lot of long time to increase the adoption.

Tried out and indeed it works! But have to wait longer, maybe it will expire in a day or two.

BTW I'm on openSUSE Tumbleweed.

Tried out and indeed it works! But have to wait longer, maybe it will expire in a day or two.

Not in my case

BTW I'm on openSUSE Tumbleweed.

Of course! you're using bleeding edge distro, so it is expected.

need instructions for the ubuntu itself !!

need instructions for the ubuntu itself !!

Only works for Ubuntu 24.10 or later from my test.

• Ensure RustDesk window is closed
• Ensure RustDesk service is active (Check if tray icon exists)

Than connect to this device, when asking, choose entire screen, and make sure you clicked "remember" or similar option.

• Ensure RustDesk window is closed

I can't as I'm connecting remotely and won't see any window till it starts working ;)

• Ensure RustDesk service is active (Check if tray icon exists)

I can't as I'm connecting remotely and won't see any tray till it starts working ;)

Service is running:

$ systemctl status rustdesk
● rustdesk.service - RustDesk
     Loaded: loaded (/etc/systemd/system/rustdesk.service; enabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf, 50-keep-warm.conf
     Active: active (running) since Sun 2025-04-06 22:37:28 CEST; 40min ago
 Invocation: 79862938b56d4cfea09b7f12c4ef9193
   Main PID: 1229 (rustdesk)
      Tasks: 7 (limit: 18046)
     Memory: 67.5M (peak: 74.4M)
        CPU: 6min 57.622s
     CGroup: /system.slice/rustdesk.service
             └─1229 /usr/bin/rustdesk --service

Than connect to this device, when asking, choose entire screen, and make sure you clicked "remember" or similar option.

If you mean some dialog on the server side then again I can't as I'm connecting remotely and won't see any window till it starts working ;)

You need to doing this physically for the first time.

And note, Wayland login screen is not supported, you need to make sure sddm is in x11 mode(You could still using Wayland session)

You need to doing this physically for the first time.

Thanks, it worked.
It would be nice to be able to choose this from the client (it's how it's normally done in remote connection software) – do you plan this?

And note, Wayland login screen is not supported, you need to make sure sddm is in x11 mode(You could still using Wayland session)

Yeah, my workaround was to enable autologin to skip sddm entirely.
Are there plans to support wayland login screen (any bug I could watch)?

Now, the problem is that mouse does not work (keyboard works). Clicks are somehow registered (which I gather from the fact that window looses focus) but the click is not registered by the window so it has no effect. I was trying to find issue for this but didn't find one. Is there one (which one) or should I raise this in a new issue?

do you plan this

I'm not devs

It would be nice to be able to choose this from the client

This is how XDG Desktop Portal works, #10016 (comment) , provided a solution that may fix this, but it need the devs to implement.

Are there plans to support wayland login screen (any bug I could watch)?

I haven't noticed one.

mouse does not work (keyboard works).

I don't have this problem, note that you should install RustDesk to your host system(*.rpm file), not through flatpak.

This is not permanent solution, this is just using x11, the x11 will deprecate in the future.

For now it works :)

For now it works :)

Everyone know changing to x11 will works, but x11 will deprecated for some distros and will not installed by default, or further, x11 will become unavailable in system repositories.

@idoCo10 Have you noticed the word Wayland in the title of this discussion?
Disabling Wayland is not the solution for the problem of not working under Wayland.

If you're on newer KDE, it means you have newer Wayland protocol, so it will able to remember the permissions already, if installed as Flatpak, the permissions of RustDesk is limited, and can't access login screen.

@xlionjuan My problem was not the permission itself, but when I connected to a remote PC, this window was waiting for a click:

RustDesk in this case just waiting for a response from the other side which is, of course, impossible.

can't access login screen.

Seems like I've already met this but it was kinda strange:

1. during a remote session I saw login screen from only one display of two (second one was black);
2. I tried to input my password but picture was frozen;
3. when I came back to this PC physically there were some characters in the password field.

No one else has access to this PC so I decided this "password" was mine. Maybe I could even blindly log in, idk

this window was waiting for a click:

I mean this can be remembered, make sure the RustDesk window is closed so this will be requested by RustDesk system service.

I mean this can be remembered

Maybe, but it didn't help at all. This window appeared every time. Once long ago I already tried to "remember" it