I am using krdpserver successfully on commandline and can connect to the machine using e.g. xfreerdp server: krdpserver -u username -p xxx --quality 100 There is also a systemsettings page called 'remote desktop' where we can define user and enable the server using a UI-toggle. see also: https://invent.kde.org/plasma/krdp/-/blob/master/README.md But, the server presumably never starts when toggling this in the UI? (contrast this to running directly on commandline, then all is fine) Moreover, i am missing feedback from the server-side, like e.g. having access to the logs from the ui to figure out any problems. (this is more of an enhancement, but a welcome one...)
(In reply to slartibart70 from comment #0) > I am using krdpserver successfully on commandline and can connect to the > machine using e.g. xfreerdp > server: krdpserver -u username -p xxx --quality 100 > > There is also a systemsettings page called 'remote desktop' where we can > define user and enable the server using a UI-toggle. > see also: https://invent.kde.org/plasma/krdp/-/blob/master/README.md > > But, the server presumably never starts when toggling this in the UI? > (contrast this to running directly on commandline, then all is fine) > > Moreover, i am missing feedback from the server-side, like e.g. having > access to the logs from the ui to figure out any problems. > (this is more of an enhancement, but a welcome one...) That is strange it works for me. Though the behavior of the server is not consistent. Sometimes the server when a client connects to it will popup a dialog asking for permission for remote access, sometimes it just works without the interactive user having to allow. I agree access to the logs from the ui to figure out any problems would rock +1 for sure. Sorry not much help but for the server logs can you try running: journalctl --user-unit=plasma-krdp_server I think that should produce the logs you are looking for.
I'm also running into this issue with Plasma 6.3.2 on Arch Linux, and I'm quite sure the GUI toggle worked just fine in either 6.1.x or 6.2.x before. If I monitor the output of "journalctl -f" the only message I get is "Toggling KRDP server to true over QDBus" and nothing else actually happens. That said, it looks like running "systemctl --user enable app-org.kde.krdpserver.service" is enough to make the GUI switch to turn on/off KRdp work for me, but turning on autostart from the GUI or the aforementioned systemctl command doesn't work with the error message "job deleted to avoid ordering cycle" from systemd.
Oh, turns out the issue I was running into is actually https://bugs.kde.org/show_bug.cgi?id=500017, which is now fixed with KDE Plasma 6.3.3.
For the bug reporter - could you please double-check if you are still experiencing the issue on Plasma 6.3.3 or later? (Thanks Prajna for the reference to that!)
Can confirm this behaviour on plasma 6.3.4 Using latest openSUSE Tumbleweed and turning checkbox "Enable RDP Server" do nothing. systemctl --user status app-org.kde.krdpserver.service ○ app-org.kde.krdpserver.service - KRDP Server Loaded: loaded (/usr/lib/systemd/user/app-org.kde.krdpserver.service; disabled; preset: disabled) Active: inactive (dead)
If the checkbox "Autostart on login" is enabled, it works, otherwise it doesn't work.