XRDP Fails to Start MATE Session on Ubuntu MATE 22.04

[EspinolaAbel]

I’m trying to connect to my Ubuntu MATE 22.04 Desktop system using XRDP, but it fails to open the desktop and an error message appears after. I attempted using as clients Windows 10 RDP, Ubuntu 24 Remmina and Lubuntu Remmina. Same result in all of them.
I can connect using ssh without problems.
The server is an OdroidXU4 board with an ARM 32b processor. At some point I was able to login via RDP but after a reboot I was never able to do it again.

Both machines are connected to my local network.

Some screenshots:

After the login the green background continues a few minutes and the error message:

Some relevant files and logs:

journalctl -u xrdp --no-pager | tail-50

Mar 18 21:43:12 odroid xrdp[1955]: [INFO ] login successful for display 10
Mar 18 21:43:12 odroid xrdp[1955]: [INFO ] loaded module 'libxup.so' ok, interface size 9456, version 4
Mar 18 21:43:12 odroid xrdp[1955]: [INFO ] started connecting
Mar 18 21:43:12 odroid xrdp[1955]: [INFO ] lib_mod_connect: connecting via UNIX socket
Mar 18 21:46:41 odroid xrdp[1955]: [INFO ] connection problem, giving up
Mar 18 21:46:41 odroid xrdp[1955]: [INFO ] some problem
Mar 18 21:47:29 odroid xrdp[1955]: [ERROR] xrdp_sec_recv: xrdp_mcs_recv failed
Mar 18 21:47:29 odroid xrdp[1955]: [ERROR] xrdp_rdp_recv: xrdp_sec_recv failed
Mar 18 21:47:29 odroid xrdp[1955]: [ERROR] libxrdp_process_data: xrdp_rdp_recv failed
Mar 18 21:47:29 odroid xrdp[1955]: [ERROR] xrdp_process_data_in: xrdp_process_loop failed
Mar 18 21:47:29 odroid xrdp[1955]: [ERROR] xrdp_iso_send: trans_write_copy_s failed
Mar 18 21:47:29 odroid xrdp[1955]: [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
Mar 18 21:47:46 odroid xrdp[745]: [INFO ] Socket 12: AF_INET6 connection received from ::ffff:192.168.0.106 port 53680
Mar 18 21:47:46 odroid xrdp[2175]: [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
Mar 18 21:47:46 odroid xrdp[2175]: [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
Mar 18 21:47:46 odroid xrdp[2175]: [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
Mar 18 21:47:46 odroid xrdp[2175]: [ERROR] libxrdp_force_read: header read error
Mar 18 21:47:46 odroid xrdp[2175]: [ERROR] Processing [ITU-T T.125] Connect-Initial failed
Mar 18 21:47:46 odroid xrdp[2175]: [ERROR] [MCS Connection Sequence] receive connection request failed
Mar 18 21:47:46 odroid xrdp[2175]: [ERROR] xrdp_sec_incoming: xrdp_mcs_incoming failed
Mar 18 21:47:46 odroid xrdp[2175]: [ERROR] xrdp_rdp_incoming: xrdp_sec_incoming failed
Mar 18 21:47:46 odroid xrdp[2175]: [ERROR] xrdp_process_main_loop: libxrdp_process_incoming failed
Mar 18 21:47:46 odroid xrdp[2175]: [ERROR] xrdp_iso_send: trans_write_copy_s failed
Mar 18 21:47:46 odroid xrdp[2175]: [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
Mar 18 21:47:48 odroid xrdp[745]: [INFO ] Socket 12: AF_INET6 connection received from ::ffff:192.168.0.106 port 53681
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
Mar 18 21:47:48 odroid xrdp[2176]: [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] Connected client computer name: DESKTOP-1N1FB5O
Mar 18 21:47:48 odroid xrdp[2176]: [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
Mar 18 21:47:48 odroid xrdp[2176]: [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x0000040A]
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [es] options []
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] Non-TLS connection established from ::ffff:192.168.0.106 port 53681: encrypted with standard RDP security
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 10485760 MB cache entries 100
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] xrdp_caps_process_codecs: nscodec, codec id 1, properties len 3
Mar 18 21:47:48 odroid xrdp[2176]: [WARN ] xrdp_caps_process_codecs: unknown codec id 5
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] xrdp_caps_process_codecs: RemoteFX, codec id 3, properties len 49
Mar 18 21:47:48 odroid xrdp[2176]: [INFO ] Loading keymap file /etc/xrdp/km-0000040a.ini
Mar 18 21:47:48 odroid xrdp[2176]: [WARN ] local keymap file for 0x0000040a found and doesn't match built in keymap, using local keymap file
Mar 18 21:48:26 odroid xrdp[2176]: [INFO ] connecting to sesman ip 127.0.0.1 port 3350
Mar 18 21:48:26 odroid xrdp[2176]: [INFO ] xrdp_wm_log_msg: sesman connect ok
Mar 18 21:48:26 odroid xrdp[2176]: [INFO ] sesman connect ok
Mar 18 21:48:26 odroid xrdp[2176]: [INFO ] sending login info to session manager, please wait...
Mar 18 21:48:26 odroid xrdp[2176]: [INFO ] xrdp_wm_log_msg: login successful for display 11
Mar 18 21:48:26 odroid xrdp[2176]: [INFO ] login successful for display 11
Mar 18 21:48:26 odroid xrdp[2176]: [INFO ] loaded module 'libxup.so' ok, interface size 9456, version 4
Mar 18 21:48:26 odroid xrdp[2176]: [INFO ] started connecting
Mar 18 21:48:26 odroid xrdp[2176]: [INFO ] lib_mod_connect: connecting via UNIX socket

/etc/xrdp/startwm.sh

#!/bin/sh
# xrdp X session start script (c) 2015, 2017, 2021 mirabilos
# published under The MirOS Licence

# Rely on /etc/pam.d/xrdp-sesman using pam_env to load both
# /etc/environment and /etc/default/locale to initialise the
# locale and the user environment properly.

if test -r /etc/profile; then
	. /etc/profile
fi

test -x /etc/X11/Xsession && exec /etc/X11/Xsession
exec /bin/sh /etc/X11/Xsession

/etc/xrdp/xrdp.ini

[Globals]
; xrdp.ini file version number
ini_version=1

; fork a new process for each incoming connection
fork=true

; ports to listen on, number alone means listen on all interfaces
; 0.0.0.0 or :: if ipv6 is configured
; space between multiple occurrences
; ALL specified interfaces must be UP when xrdp starts, otherwise xrdp will fail to start
;
; Examples:
;   port=3389
;   port=unix://./tmp/xrdp.socket
;   port=tcp://.:3389                           127.0.0.1:3389
;   port=tcp://:3389                            *:3389
;   port=tcp://<any ipv4 format addr>:3389      192.168.1.1:3389
;   port=tcp6://.:3389                          ::1:3389
;   port=tcp6://:3389                           *:3389
;   port=tcp6://{<any ipv6 format addr>}:3389   {FC00:0:0:0:0:0:0:1}:3389
;   port=vsock://<cid>:<port>
port=3389

; 'port' above should be connected to with vsock instead of tcp
; use this only with number alone in port above
; prefer use vsock://<cid>:<port> above
use_vsock=false

; regulate if the listening socket use socket option tcp_nodelay
; no buffering will be performed in the TCP stack
tcp_nodelay=true

; regulate if the listening socket use socket option keepalive
; if the network connection disappear without close messages the connection will be closed
tcp_keepalive=true

; set tcp send/recv buffer (for experts)
#tcp_send_buffer_bytes=32768
#tcp_recv_buffer_bytes=32768

; security layer can be 'tls', 'rdp' or 'negotiate'
; for client compatible layer
security_layer=negotiate

; minimum security level allowed for client for classic RDP encryption
; use tls_ciphers to configure TLS encryption
; can be 'none', 'low', 'medium', 'high', 'fips'
crypt_level=high

; X.509 certificate and private key
; openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem -days 365
; note this needs the user xrdp to be a member of the ssl-cert group, do with e.g.
;$ sudo adduser xrdp ssl-cert
certificate=
key_file=

; set SSL protocols
; can be comma separated list of 'SSLv3', 'TLSv1', 'TLSv1.1', 'TLSv1.2', 'TLSv1.3'
ssl_protocols=TLSv1.2, TLSv1.3
; set TLS cipher suites
#tls_ciphers=HIGH

; concats the domain name to the user if set for authentication with the separator
; for example when the server is multi homed with SSSd
#domain_user_separator=@

; The following options will override the keyboard layout settings.
; These options are for DEBUG and are not recommended for regular use.
#xrdp.override_keyboard_type=0x04
#xrdp.override_keyboard_subtype=0x01
#xrdp.override_keylayout=0x00000409

; Section name to use for automatic login if the client sends username
; and password. If empty, the domain name sent by the client is used.
; If empty and no domain name is given, the first suitable section in
; this file will be used.
autorun=

allow_channels=true
allow_multimon=true
bitmap_cache=true
bitmap_compression=true
bulk_compression=true
#hidelogwindow=true
max_bpp=32
new_cursors=true
; fastpath - can be 'input', 'output', 'both', 'none'
use_fastpath=both
; when true, userid/password *must* be passed on cmd line
#require_credentials=true
; when true, the userid will be used to try to authenticate
#enable_token_login=true
; You can set the PAM error text in a gateway setup (MAX 256 chars)
#pamerrortxt=change your password according to policy at http://url

;
; colors used by windows in RGB format
;
blue=009cb5
grey=dedede
#black=000000
#dark_grey=808080
#blue=08246b
#dark_blue=08246b
#white=ffffff
#red=ff0000
#green=00ff00
#background=626c72

;
; configure login screen
;

; Login Screen Window Title
#ls_title=My Login Title

; top level window background color in RGB format
ls_top_window_bg_color=009cb5

; width and height of login screen
;
; The default height allows for about 5 fields to be comfortably displayed
; above the buttons at the bottom. To display more fields, make <ls_height>
; larger, and also increase <ls_btn_ok_y_pos> and <ls_btn_cancel_y_pos>
; below
;
ls_width=350
ls_height=430

; login screen background color in RGB format
ls_bg_color=dedede

; optional background image filename (bmp format).
#ls_background_image=

; logo
; full path to bmp-file or file in shared folder
ls_logo_filename=
ls_logo_x_pos=55
ls_logo_y_pos=50

; for positioning labels such as username, password etc
ls_label_x_pos=30
ls_label_width=65

; for positioning text and combo boxes next to above labels
ls_input_x_pos=110
ls_input_width=210

; y pos for first label and combo box
ls_input_y_pos=220

; OK button
ls_btn_ok_x_pos=142
ls_btn_ok_y_pos=370
ls_btn_ok_width=85
ls_btn_ok_height=30

; Cancel button
ls_btn_cancel_x_pos=237
ls_btn_cancel_y_pos=370
ls_btn_cancel_width=85
ls_btn_cancel_height=30

[Logging]
; Note: Log levels can be any of: core, error, warning, info, debug, or trace
LogFile=xrdp.log
LogLevel=INFO
EnableSyslog=true
#SyslogLevel=INFO
#EnableConsole=false
#ConsoleLevel=INFO
#EnableProcessId=false

[LoggingPerLogger]
; Note: per logger configuration is only used if xrdp is built with
; --enable-devel-logging
#xrdp.c=INFO
#main()=INFO

[Channels]
; Channel names not listed here will be blocked by XRDP.
; You can block any channel by setting its value to false.
; IMPORTANT! All channels are not supported in all use
; cases even if you set all values to true.
; You can override these settings on each session type
; These settings are only used if allow_channels=true
rdpdr=true
rdpsnd=true
drdynvc=true
cliprdr=true
rail=true
xrdpvr=true
tcutils=true

; for debugging xrdp, in section xrdp1, change port=-1 to this:
#port=/tmp/.xrdp/xrdp_display_10


;
; Session types
;

; Some session types such as Xorg, X11rdp and Xvnc start a display server.
; Startup command-line parameters for the display server are configured
; in sesman.ini. See and configure also sesman.ini.
[Xorg]
name=Xorg
lib=libxup.so
username=ask
password=ask
ip=127.0.0.1
port=-1
code=20

[Xvnc]
name=Xvnc
lib=libvnc.so
username=ask
password=ask
ip=127.0.0.1
port=-1
#xserverbpp=24
#delay_ms=2000
; Disable requested encodings to support buggy VNC servers
; (1 = ExtendedDesktopSize)
#disabled_encodings_mask=0
; Use this to connect to a chansrv instance created outside of sesman
; (e.g. as part of an x11vnc console session). Replace '0' with the
; display number of the session
#chansrvport=DISPLAY(0)

; Generic VNC Proxy
; Tailor this to specific hosts and VNC instances by specifying an ip
; and port and setting a suitable name.
[vnc-any]
name=vnc-any
lib=libvnc.so
ip=ask
port=ask5900
username=na
password=ask
#pamusername=asksame
#pampassword=asksame
#pamsessionmng=127.0.0.1
#delay_ms=2000

; Generic RDP proxy using NeutrinoRDP
; Tailor this to specific hosts by specifying an ip and port and setting
; a suitable name.
[neutrinordp-any]
name=neutrinordp-any
; To use this section, you should build xrdp with configure option
; --enable-neutrinordp.
lib=libxrdpneutrinordp.so
ip=ask
port=ask3389
username=ask
password=ask
; Uncomment the following lines to enable PAM authentication for proxy
; connections.
#pamusername=ask
#pampassword=ask
#pamsessionmng=127.0.0.1
; Currently NeutrinoRDP doesn't support dynamic resizing. Uncomment
; this line if you're using a client which does.
#enable_dynamic_resizing=false
; By default, performance settings requested by the RDP client are ignored
; and chosen by NeutrinoRDP. Uncomment this line to allow the user to
; select performance settings in the RDP client.
#perf.allow_client_experiencesettings=true
; Override any experience setting by uncommenting one or more of the
; following lines.
#perf.wallpaper=false
#perf.font_smoothing=false
#perf.desktop_composition=false
#perf.full_window_drag=false
#perf.menu_anims=false
#perf.themes=false
#perf.cursor_blink=false
; By default NeutrinoRDP supports cursor shadows. If this is giving
; you problems (e.g. cursor is a black rectangle) try disabling cursor
; shadows by uncommenting the following line.
#perf.cursor_shadow=false
; By default, NeutrinoRDP uses the keyboard layout of the remote RDP Server.
; If you want to tell the remote the keyboard layout of the RDP Client,
; by uncommenting the following line.
#neutrinordp.allow_client_keyboardLayout=true
; The following options will override the remote keyboard layout settings.
; These options are for DEBUG and are not recommended for regular use.
#neutrinordp.override_keyboardLayout_mask=0x0000FFFF
#neutrinordp.override_kbd_type=0x04
#neutrinordp.override_kbd_subtype=0x01
#neutrinordp.override_kbd_fn_keys=12
#neutrinordp.override_kbd_layout=0x00000409

; You can override the common channel settings for each session type
#channel.rdpdr=true
#channel.rdpsnd=true
#channel.drdynvc=true
#channel.cliprdr=true
#channel.rail=true
#channel.xrdpvr=true

~/.xsession

mate-session

~/.xsession-errors

Xsession: X session started for odroid at Tue Mar 18 21:17:19 -03 2025
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:10.0
xrdb: Connection refused
xrdb: Can't open display ':10.0'
xhost:  unable to open display ":10.0"
Error opening display!
xhost:  unable to open display ":10.0"
dbus-update-activation-environment: setting GTK_MODULES=appmenu-gtk-module:gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=odroid
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/odroid
dbus-update-activation-environment: setting GTK_MODULES=appmenu-gtk-module:gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting UBUNTU_MENUPROXY=1
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting LOGNAME=odroid
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/odroid
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/gnome:/home/odroid/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop
Xsession: X session started for odroid at Tue Mar 18 21:43:12 -03 2025
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:10.0
xrdb: Connection refused
xrdb: Can't open display ':10.0'
xhost:  unable to open display ":10.0"
Error opening display!
xhost:  unable to open display ":10.0"
dbus-update-activation-environment: setting GTK_MODULES=appmenu-gtk-module:gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=odroid
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/odroid
dbus-update-activation-environment: setting GTK_MODULES=appmenu-gtk-module:gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_10
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_10
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting UBUNTU_MENUPROXY=1
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting LOGNAME=odroid
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:10.0
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/odroid
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/gnome:/home/odroid/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop

** (mate-session:2165): WARNING **: 21:43:14.987: Cannot open display: 
Xsession: X session started for odroid at Tue Mar 18 21:48:26 -03 2025
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting DISPLAY=:11.0
xrdb: Connection refused
xrdb: Can't open display ':11.0'
xhost:  unable to open display ":11.0"
Error opening display!
xhost:  unable to open display ":11.0"
dbus-update-activation-environment: setting GTK_MODULES=appmenu-gtk-module:gail:atk-bridge
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting USER=odroid
dbus-update-activation-environment: setting XDG_SESSION_TYPE=x11
dbus-update-activation-environment: setting HOME=/home/odroid
dbus-update-activation-environment: setting GTK_MODULES=appmenu-gtk-module:gail:atk-bridge
dbus-update-activation-environment: setting XRDP_PULSE_SINK_SOCKET=xrdp_chansrv_audio_out_socket_11
dbus-update-activation-environment: setting XRDP_PULSE_SOURCE_SOCKET=xrdp_chansrv_audio_in_socket_11
dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
dbus-update-activation-environment: setting UBUNTU_MENUPROXY=1
dbus-update-activation-environment: setting PULSE_SCRIPT=/etc/xrdp/pulse/default.pa
dbus-update-activation-environment: setting IM_CONFIG_PHASE=1
dbus-update-activation-environment: setting LOGNAME=odroid
dbus-update-activation-environment: setting XDG_SESSION_CLASS=user
dbus-update-activation-environment: setting PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
dbus-update-activation-environment: setting XRDP_SOCKET_PATH=/run/xrdp/sockdir
dbus-update-activation-environment: setting XDG_RUNTIME_DIR=/run/user/1000
dbus-update-activation-environment: setting DISPLAY=:11.0
dbus-update-activation-environment: setting UID=1000
dbus-update-activation-environment: setting SHELL=/bin/bash
dbus-update-activation-environment: setting QT_ACCESSIBILITY=1
dbus-update-activation-environment: setting XRDP_SESSION=1
dbus-update-activation-environment: setting GPG_AGENT_INFO=/run/user/1000/gnupg/S.gpg-agent:0:1
dbus-update-activation-environment: setting PWD=/home/odroid
dbus-update-activation-environment: setting XDG_DATA_DIRS=/usr/share/gnome:/home/odroid/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop

** (mate-session:2390): WARNING **: 21:48:29.120: Cannot open display: 

I’d greatly appreciate any insights or guidance on resolving this.

[matt335672]

Hi @EspinolaAbel

I'm sorry to be a nuisance, but could you do the following:-

1. Have a look at previous issues which match this. Here are a few:-
   https://github.com/neutrinolabs/xrdp/issues?q=is%3Aissue%20ubuntu%20%22connection%20problem%22
2. (Assuming you can't find it). Open an bug report on this and fill in the details

Filling in the bug report saves lot of time in the long run for all of us in the xrdp community:-

1. We get a lot of information about your installation without having to go backwards and forwards.
2. Users who have the same issue are more likely to find it in the 'issues' section.

Thanks.