Created attachment 186585 [details] krdc.log SUMMARY Unable to remotely connect from Plasma DE to Plasma DE (KRDC -> KRDP), because of a blue screen. All stuffs I use is pure KDE stuff. Marking the ticket as critical, since this is an essential thing in our household and in general (remote is there so one does not have to physically walk around), and currently I'm unable to remote to my parent's computers when they need help, so I have to take a long walk, instead of just simply remoting into their machines. STEPS TO REPRODUCE Attempt remote connecting from KRDC, into a machine that has KRDP set up. OBSERVED RESULT Blue screen and an error message afterwards, that it's unable to connect. EXPECTED RESULT Should work, and connect remotely. SOFTWARE/OS VERSIONS (both of my computers) : Operating System: Kubuntu 25.10 KDE Plasma Version: 6.5.2 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.2 Kernel Version: 6.17.0-6-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 16 GiB of RAM (15.6 GiB usable) Graphics Processor: NVIDIA GeForce GTX 1050 Ti Manufacturer: MSI Product Name: MS-7972 System Version: 2.0 ADDITIONAL INFO: Also tried this by toggling firewalls on and off, and checked KRDP side all set multiple times! I remember this thing being broken for a while, I recall this when KRDP was announced being baked in Plasma Settings, since then I can't rely on this thing. It sometimes works, but most of the times it doesn't work.. I don't know if it's KRDP or KRDC side, maybe both...
Created attachment 186586 [details] screenshot of bluescreen
As the logs says: "failed to connect". Either a wrong ip address, a firewall blocking the connection or something similar. Are you able to connect with another client? eg freerdp, remmina, ..
(In reply to Fabio from comment #2) > As the logs says: "failed to connect". Either a wrong ip address, a firewall > blocking the connection or something similar. > Are you able to connect with another client? eg freerdp, remmina, .. No dawg, the IP address is not wrong ..... 🙄 🤦🤦🤦 and as I said I tried it with firewalls off and on, and the problem still persisted... Why asking these? Have you actually tried this on your end, to connect to your KRDP from KRDC and it works for you? I don't know about remmina, or freerdp and I won't even bother those, on a KDE bug platform let's focus on KDE related stuffs as those are the bugged ones, in this case KRDC and KRDP and not hijack to different programms, allright?
(In reply to Sylens from comment #3) > No dawg, the IP address is not wrong ..... 🙄 🤦🤦🤦 > and as I said I tried it with firewalls off and on, and the problem still > persisted... The only thing that we can determine from the error message in the logs is that there's nothing listening for a connection on that IP. > Why asking these? Have you actually tried this on your end, to connect to > your KRDP from KRDC and it works for you? Of course I tried. As a krdc developer I do dozens of connections while testing changes. For me it's working just fine, and I guess it's the same for just everybody else, otherway we would be flooded by bug reports. > I don't know about remmina, or freerdp and I won't even bother those, on a > KDE bug platform let's focus on KDE related stuffs as those are the bugged > ones, in this case KRDC and KRDP and not hijack to different programms, > allright? This is called basic debugging. You have a problem somewhere between a server (krdp) and a client (krdc). Try to swap one of the two components with something else, and see if it works. The easiest thing to swap is the client, so trying another client would let you know if the problem is krdc or krdp. I'm not sure how much I can help you if you don't want to do basic testing to determine the cause of the problem.
(In reply to Fabio from comment #4) > > The only thing that we can determine from the error message in the logs is > that there's nothing listening for a connection on that IP. Well KRDP is turned on, so it's listening, on 3389, firewalls are off on both sides. Maybe it's a KRDP issue, I don't know cause the two are not very transparent or talkative when it comes to debugging. I remember it worked when X11+Krfb was a thing, but since Wayland+KRDP came in the picture, RDP started acting odd (forum / reddit links next section) > Of course I tried. As a krdc developer I do dozens of connections while > testing changes. > For me it's working just fine, and I guess it's the same for just everybody > else, otherway we would be flooded by bug reports. Yeah, one should not rely on mere assumptions. It only took me a good five seconds to do a google search about this problem, and find the same symptoms many users had/have (and gave up doing their research midway), so on the contrary, they are flooding, but at the wrong place.. (forums e.g. https://discuss.kde.org/t/krdp-remote-desktop-not-functioning-correctly or https://discuss.kde.org/t/krdp-and-apache-guacamole/18155 or https://www.reddit.com/r/kde/comments/1gg7ny8/krdp_not_working_on_tumbleweed/ ) - that's why I came here on bugzilla, cause I know where to place this long standing issue. People are lost, they are clueless whenever it comes to of how or where to do bugreports, or better yet -whoever does know of how or where to do it, they just simply don't bother reporting it, because "oh someone else will do it for me". Here I (someone else) am, months/years later cause it bugged my head long enough to report it... > This is called basic debugging. You have a problem somewhere between a > server (krdp) and a client (krdc). > Try to swap one of the two components with something else, and see if it > works. > The easiest thing to swap is the client, so trying another client would let > you know if the problem is krdc or krdp. > > I'm not sure how much I can help you if you don't want to do basic testing > to determine the cause of the problem. I know, it's technically called debug by isolation. I tried with Remmina, same symptoms. journalctl -f -p0..7 gives out a yuv240 not supported in h264 mode, but doesn't really matter, I tried with every single variation a men can think of, to no avail. I think this is more KRDP+Wayland issue related than KRDC, so I'm moving this ticket under KRDP. Furthermore, I'll attach a journal log about the "Client does not support H.264 in YUV420 mode!"
Created attachment 186680 [details] journal
Ok, the "Client does not support H.264 in YUV420 mode!" is something I've already dealt with. It could be this issue: https://invent.kde.org/neon/backports-noble/freerdp3-noble/-/commit/72a2135cdb35c5ddb92564a7974583cfe7147f5d Both krdc and krdp are using libfreerdp3 to implement the rdp functionality. While krdc supports all the graphic pipelines from libfreerdp3, krdp only supports H.264+YUV420 since that's what it gets whils screen recording from PipeWire. Unfortunately Ubuntu explicitly disables ffmpeg supports in freerdp (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880157, https://packages.ubuntu.com/questing/libfreerdp3-3) So, krdc (and other libfreerdp-based rdp clients in ubuntu) lacks h264 support because of the missing ffmpeg, while krdp only supports h264. In KDE Neon (basically ubuntu+kde) we patch the ubuntu package to re-enable ffmpeg support. Possible fixes/workround: * implement other graphics pipelines in krdp; * use different freerdp/krdc/remmina packages, either from kde neon or flatpacks (at least the krdc flatpak includes ffmpeg support) * if you were ok with Krfb (aka VNC), it's still available and it should work under wayland.
(In reply to Fabio from comment #7) > Ok, the "Client does not support H.264 in YUV420 mode!" is something I've > already dealt with. > It could be this issue: > https://invent.kde.org/neon/backports-noble/freerdp3-noble/-/commit/ > 72a2135cdb35c5ddb92564a7974583cfe7147f5d > Both krdc and krdp are using libfreerdp3 to implement the rdp functionality. > While krdc supports all the graphic pipelines from libfreerdp3, krdp only > supports H.264+YUV420 since that's what it gets whils screen recording from > PipeWire. > Unfortunately Ubuntu explicitly disables ffmpeg supports in freerdp > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880157, > https://packages.ubuntu.com/questing/libfreerdp3-3) > So, krdc (and other libfreerdp-based rdp clients in ubuntu) lacks h264 > support because of the missing ffmpeg, while krdp only supports h264. > In KDE Neon (basically ubuntu+kde) we patch the ubuntu package to re-enable > ffmpeg support. > Possible fixes/workround: > * implement other graphics pipelines in krdp; > * use different freerdp/krdc/remmina packages, either from kde neon or > flatpacks (at least the krdc flatpak includes ffmpeg support) > * if you were ok with Krfb (aka VNC), it's still available and it should > work under wayland. Ah thanks, this thing drove me crazy - I should have known it was an Ubuntu thing (yet again lol) :D Ok, for now as a workaround I use Krfb (since I'm a KDE fan, I use only KDE stuffs hehe) I hope KRDP gets somehow implemented on Ubuntu based systems too. Do you know where should I go with this? Launchpad and suggest them to include ffmpeg in freerdp3? For me it's still unclear, of why they removed ffmpeg support only from freerdp3, while ffmpeg itself is in their repos (and is installed on my system)