![](https://seccdn.libravatar.org/avatar/b412e0e96b356608cdeaf4428d35ac4f.jpg?s=120&d=mm&r=g)
On 3/28/24 18:25, Pablo Sanchez wrote:
On 2024-03-28 18:20, Joe Salmeri wrote:
I am debugging trying to debug a problem with Krdc to determine if it is a plasma 6 issue.
Hi Joe,
Is it possible that you are hitting this bug - https://bugs.kde.org/show_bug.cgi?id=482950
My current work-around is to use TigerVNC. :\
Thx!
Thanks Pablo, I just read though that bug report. It "could" be related, but to me there is a KEY difference. krdc works FINE with my Linux RDP server (running xrdp) when it is using the OLD-NAME for the server. If I rename the server to NEW-NAME then krdc has the blue screen issues and does not work. If I rename the server back to OLD-NAME then krdc works again. I've been talking to the xrdp developer about this ( even though it does not appear to be an xrdp problem since xfreerdp works ) and he is in agreement that krdc is having TLS certificate issue when the server is renamed causing the failure. I have also used strace to look at every file that is accessed by krdc on the client but found nothing BUT more importantly since I built a new TW client machine it too fails with NEW-NAME that confirms that something on the RDP server side is causing the certificate issue. They question is what ??? I have not found out what tool to use on TW to view all the client and server certificates. -- Regards, Joe