https://bugs.kde.org/show_bug.cgi?id=511773
--- Comment #5 from Sylens <[email protected]> --- (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!" -- You are receiving this mail because: You are watching all bug changes.
