RDP issue

[khobar]

Hello,

I've Googled for a solution without success.

Today, I set up a Le Potato w/Armbian XFCE 22.04. All was well except only root had RDP access. After trying various ideas from the internet, I still can't get in as a normal user.

 

After the last attempt, I see this in /var/log/xrdp.log:
[20220830-08:06:43] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:192.168.50.226 port 63884
[20220830-08:06:43] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20220830-08:06:43] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20220830-08:06:43] [ERROR] SSL_read: I/O error
[20220830-08:06:43] [ERROR] libxrdp_force_read: header read error
[20220830-08:06:43] [ERROR] Processing [ITU-T T.125] Connect-Initial failed
[20220830-08:06:43] [ERROR] [MCS Connection Sequence] receive connection request failed
[20220830-08:06:43] [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
[20220830-08:06:43] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20220830-08:06:43] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20220830-08:06:43] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20220830-08:06:43] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20220830-08:06:43] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:192.168.50.226 port 63885
[20220830-08:06:43] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20220830-08:06:43] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20220830-08:06:43] [INFO ] Connected client computer name: YOGAS1
[20220830-08:06:43] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20220830-08:06:43] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20220830-08:06:43] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00000409]
[20220830-08:06:43] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [us] options []
[20220830-08:06:43] [INFO ] TLS connection established from ::ffff:192.168.50.226 port 63885: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384
[20220830-08:06:43] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20220830-08:06:43] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 10485760 MB cache entries 100
[20220830-08:06:43] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20220830-08:06:43] [WARN ] xrdp_caps_process_codecs: unknown codec id 5
[20220830-08:06:43] [INFO ] xrdp_caps_process_codecs: RemoteFX, codec id 3, properties len 49
[20220830-08:06:43] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[20220830-08:06:43] [WARN ] local keymap file for 0x00000409 found and doesn't match built in keymap, using local keymap file
[20220830-08:06:43] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20220830-08:06:43] [INFO ] started connecting
[20220830-08:06:43] [INFO ] lib_mod_connect: connecting via TCP socket

Basically, I get a black screen. 

For grins, I looked up how to enable RDP on my Raspberry Pi 4 running Raspbian Bullseye - basically do an apt-get install xrdp and done. Sure enough, I did that and sure enough, I am able to RDP into my Pi no problem.

So, what am I missing???

 

Thx.

Khobar

[kyliael]

Same issue here. Tried some workaround found on the forum, but basically the issue is simple : Only Root can be used to RDP. Using any other user just close the RDP.

( Tinkerboard S )

[Myron]

I had the opposite problem. When I tried to sign in as root I got a black screen and the RDP session terminated, but a normal Linux user RDP session is stable.

Turns out I had a .xsession file in root's home directory with a command that didn't exist. When I renamed this file to something else then RDP started correctly when using root.

[gucki]

I had the same problem. After deleting the .Xauthority file in the home directory, the RDP session remains stable. I did not check the sense of the cookie file .Xauthority or whether there are other and better workarounds. Let me know when you found the real bug or config problem.