Why is my connection is closing after successful login?

[Marco-Gtto]

Hi,
i know, there are several issues about this problem, but i spent the whole day trying to figuring out what is wrong and nothing is working.

Here some logs. I saw something bad about ssl-cert but i've no idea if that's the cause.

[20220911-22:21:14] [INFO ] Received termination signal, stopping the server accept new connections thread
[20220911-22:21:14] [INFO ] address [0.0.0.0] port [3389] mode 1
[20220911-22:21:14] [INFO ] listening to port 3389 on 0.0.0.0
[20220911-22:21:14] [INFO ] xrdp_listen_pp done
[20220911-22:21:16] [INFO ] starting xrdp with pid 7712
[20220911-22:21:16] [INFO ] address [0.0.0.0] port [3389] mode 1
[20220911-22:21:16] [INFO ] listening to port 3389 on 0.0.0.0
[20220911-22:21:16] [INFO ] xrdp_listen_pp done
[20220911-22:21:17] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:293.60.42.78 port 41590
[20220911-22:21:17] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20220911-22:21:17] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20220911-22:21:17] [INFO ] Socket 12: AF_INET6 connection received from ::ffff:293.60.42.78 port 41606
[20220911-22:21:17] [ERROR] SSL_read: Failure in SSL library (protocol error?)
[20220911-22:21:17] [ERROR] SSL: error:0A000126:SSL routines::unexpected eof while reading
[20220911-22:21:17] [ERROR] libxrdp_force_read: header read error
[20220911-22:21:17] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20220911-22:21:17] [ERROR] Processing [ITU-T T.125] Connect-Initial failed
[20220911-22:21:17] [ERROR] [MCS Connection Sequence] receive connection request failed
[20220911-22:21:17] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20220911-22:21:17] [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
[20220911-22:21:17] [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
[20220911-22:21:17] [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
[20220911-22:21:17] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[20220911-22:21:17] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[20220911-22:21:17] [INFO ] Connected client computer name: DESKTOP-AQ7JFNU
[20220911-22:21:17] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[20220911-22:21:17] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[20220911-22:21:18] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00000410]
[20220911-22:21:18] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [it] options []
[20220911-22:21:18] [INFO ] TLS connection established from ::ffff:293.60.42.78 port 41606: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384
[20220911-22:21:18] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[20220911-22:21:18] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 10485760 MB cache entries 100
[20220911-22:21:18] [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
[20220911-22:21:18] [WARN ] xrdp_caps_process_codecs: unknown codec id 5
[20220911-22:21:18] [INFO ] xrdp_caps_process_codecs: RemoteFX, codec id 3, properties len 49
[20220911-22:21:18] [INFO ] Loading keymap file /etc/xrdp/km-00000410.ini
[20220911-22:21:18] [WARN ] local keymap file for 0x00000410 found and doesn't match built in keymap, using local keymap file
[20220911-22:21:24] [INFO ] connecting to sesman ip 127.0.0.1 port 3350
[20220911-22:21:24] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20220911-22:21:24] [INFO ] sesman connect ok
[20220911-22:21:24] [INFO ] sending login info to session manager, please wait...
[20220911-22:21:24] [INFO ] xrdp_wm_log_msg: login successful for display 11
[20220911-22:21:24] [INFO ] login successful for display 11
[20220911-22:21:24] [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4
[20220911-22:21:24] [INFO ] started connecting
[20220911-22:21:24] [INFO ] lib_mod_connect: connecting via UNIX socket
[20220911-22:21:24] [INFO ] lib_mod_log_peer: xrdp_pid=7715 connected to X11rdp_pid=7721 X11rdp_uid=1001 X11rdp_gid=1001 client_ip=::ffff:193.70.42.88 client_port=41606
[20220911-22:21:24] [INFO ] connected ok

I've xfce4 installed and setted up as default.
Let me know what else you need

Thank you

[matt335672]

ssl-cert isn't a problem as far as making a connection goes. To fix it, add the xrdp user to the ssl-cert group. See here for more details.

Your log above looks fine. The xrdp process is connecting to sesman and asking sesman to create a session. sesman is replying and saying that's done. xrdp is then connection to the session.

Here are some possible reasons:-

• The most likely reason is that you've got another graphical session logged in as the same user. This most normally happens if the console is logged in as the same user you're trying to use for xrdp. Modern systemd-based distributions don't allow the same user to be logged in to two graphical sessions at once on the same machine. If you really need that functionality, used a non-systemd distribution, or FreeBSD where everything works fine.
• The X server may be failing. Have a look in ~/.xorgxrdp.11.log for a log of the X server.
• You need to configure your session manager as XFCE4 using update-alternatives. See this post
• You've got a ~/.xsession or ~/.Xsession file which is mis-configured
• Your home directory is not writeable, possibly because the disk is full.

If none of those give you any joy, gave a look in ~/.xsession-errors fo any possible error messages relating to the session.

Please report back with what you find - it may help someone else in the future.

[Marco-Gtto]

Hey @matt335672,
thank you so much for the detailed explanation.

Googling around this issue i added following strings to startwm.sh:

unset DBUS_SESSION_BUS_ADDRESS
unset XDG_RUNTIME_DIR

At least for now it is working. Can you explain to me what those strings are doing?

[matt335672]

They work around the first problem in the list above. With some desktops you might get away with it, but odd things can happen particularly with GNOME.

Best advice on systemd-based distributions is to use a different user name for xrdp connections.

[akarl10]

while I doubt that this will be solved in systemd in the near future I have added a RFE on systemd
systemd/systemd#24932
basically for a gnome session the biggest issue is that parts of the session are started as systemd.user units and systemd does not have "systemd.session" units. It has however the concept of a session, so systemd.session units should be doable and imho make also sense, systemd has also a multiseat concept, but running session services in a global user scope effectively defeats this idea if a user is able to create more than one session.
KDE/plasma currently does not use systemd.user units so much, but sound daemons nowadays are started in a user global scope. Here if you login with xrdp and you are logged in on a physical desktop, you will steal the sound of the previous session 🤫

[Marco-Gtto]

Hey @akarl10,
my knowledge about linux systems is based on how to use and code on them so i have never studied their core. Anyway i read your issue on systemd and is pretty understandable also for me. Surely, if it is possible, would be a solution to make our work easier. 😄

[matt335672]

@akarl10 - nice work. As you say, starting the discussion is well worth doing.