https://bugs.kde.org/show_bug.cgi?id=482950
Joe S <jmscdba+...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jmscdba+...@gmail.com
--- Comment #6 from Joe S <jmscdba+...@gmail.com> ---
I am having a similar problem and have spent DAYS debugging what is going on
although my situation is slightly different, I think it may point to the root
cause.
I am running Tumbleweed 20240319 which has krdc 24.02.0-1.1 but I have
replicated the problem on a test machine which is running TW 20240328 ( the
latest ) and using krdc 24-02.1-1.1.
In my case, initially I have no problems using krdc to connect to the xrdp
server.
BUT, I need to rename the server that is hosting xrdp and after I rename the
server from OLD-NAME to NEW-NAME then BOTH krdc 24.02.0-1.1 and krdc
24.02.1-1.1 experience the BLUE screen and do not get the desktop.
Although either krdc version has the blue screen problem, I have no problems
remotely connecting using xfreerdp or remmina to the NEW-NAME server and ping
and ssh also work using the NEW-NAME.
Even Windows 10 clients can connect to NEW-NAME with no issues.
Generally the other clients display a unknown certificate error but after you
accept and continue then your are logged in and the desktop is displayed.
If I rename the server back to OLD-NAME then krdc starts working again.
If I rename the server back to NEW-NAME then krdc gets the blue screen again
and yet EVERYTHING else works fine with NEW-NAME.
I even went as far as building a new VM with a fresh TW install and that VM
experiences the same issues.
On TW, xrdp uses /usr/bin/xrdp-keygen to generate /etc/xrdp/rsakeys.ini which
has the key/cert used by the xrdp connections.
If you generate your own key/cert and then modify /etc/xrdp/xrdp.ini to set the
certificate= and file_key= lines to the generated files and then restart the
xrdp service, then all clients work with NEW-NAME ( after accepting the unknown
certificate ) except for krdc.
For krdc it displays the unknown certificate message ( unlike when using the
keys from rsakeys.ini ) but after selecting Continue you are still left with
the blue screen. At one point I even heard the login sound play but still no
desktop is displayed with krdc.
Since everything else works fine with the NEW-NAME for the server EXCEPT for
krdc that seems to point to it being the problem.
NOTE: I have renamed xrdp servers in the past and have not run into this
problem.
Hopefully my detailed analysis helps you to identify what is wrong with krdc.
Please let me know if you want more details.
--
You are receiving this mail because:
You are watching all bug changes.
