Skip to content

Black screen after login, followed by disconnect #2560

Description

@blaizmannen

Running on ubuntu 22.04 on an EC2 instance.

Was running fine for a few months, but following a recent apt update on this instance, xrdp fails to work. I would be met with a black screen for a few seconds, follow by an abrupt exit of my window. I am using Microsoft Remote Desktop from a macOS machine.

xrdp-sesman.log excerpts from reboot up until an xrdp login attempt:


[20230221-09:21:21] [DEBUG] libscp initialized
[20230221-09:21:21] [DEBUG] Testing if xrdp-sesman can listen on 127.0.0.1 port 3350.
[20230221-09:21:21] [DEBUG] Closed socket 6 (AF_INET6 ::1 port 3350)
[20230221-09:21:21] [INFO ] starting xrdp-sesman with pid 577
[20230221-09:21:21] [DEBUG] sesman_main_loop: address 127.0.0.1 port 3350
[20230221-09:25:28] [INFO ] Socket 9: AF_INET6 connection received from ::1 port 35178
[20230221-09:25:45] [DEBUG] session_get_bydata: search policy 0 U user.name W 1512 H 944 bpp 24 T 3 IP 10.50.1.112:57836 - socket: 12
[20230221-09:25:45] [INFO ] Terminal Server Users group is disabled, allowing authentication
[20230221-09:25:45] [INFO ] ++ created session (access granted): username user.name, ip 10.50.1.112:57836 - socket: 12
[20230221-09:25:45] [INFO ] starting Xorg session...
[20230221-09:25:45] [DEBUG] Did not find a running X server at /tmp/.X11-unix/X10
[20230221-09:25:45] [DEBUG] Did not find a running X server at /tmp/.X10-lock
[20230221-09:25:45] [DEBUG] Closed socket 14 (AF_INET6 :: port 5910)
[20230221-09:25:45] [DEBUG] Did not find a running X server at 5910
[20230221-09:25:45] [DEBUG] Closed socket 14 (AF_INET6 :: port 6010)
[20230221-09:25:45] [DEBUG] Did not find a running X server at 6010
[20230221-09:25:45] [DEBUG] Closed socket 14 (AF_INET6 :: port 6210)
[20230221-09:25:45] [DEBUG] Did not find a running X server at 6210
[20230221-09:25:45] [DEBUG] Did not find a running X server at /run/xrdp/sockdir/xrdp_chansrv_socket_10
[20230221-09:25:45] [DEBUG] Did not find a running X server at /run/xrdp/sockdir/xrdp_chansrv_audio_out_socket_10
[20230221-09:25:45] [DEBUG] Did not find a running X server at /run/xrdp/sockdir/xrdp_chansrv_audio_in_socket_10
[20230221-09:25:45] [DEBUG] Did not find a running X server at /run/xrdp/sockdir/xrdpapi_10
[20230221-09:25:45] [INFO ] Starting session: session_pid 1168, display :10.0, width 1512, height 944, bpp 24, client ip 10.50.1.112:57836 - socket: 12, user name user.name
[20230221-09:25:45] [INFO ] [session start] (display 10): calling auth_start_session from pid 1168
[20230221-09:25:45] [ERROR] sesman_data_in: scp_process_msg failed
[20230221-09:25:45] [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
[20230221-09:25:45] [DEBUG] Closed socket 9 (AF_INET6 ::1 port 3350)
[20230221-09:25:45] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20230221-09:25:45] [DEBUG] Closed socket 9 (AF_INET6 ::1 port 3350)
[20230221-09:25:45] [DEBUG] Waiting for X server to start on display 10
[20230221-09:25:45] [DEBUG] Did not find a running X server at /tmp/.X11-unix/X10
[20230221-09:25:45] [DEBUG] Waiting for X server to start on display 10
[20230221-09:25:45] [DEBUG] Did not find a running X server at /tmp/.X11-unix/X10
[20230221-09:25:45] [DEBUG] Did not find a running X server at /tmp/.X10-lock
[20230221-09:25:45] [DEBUG] Did not find a running X server at /tmp/.X10-lock
[20230221-09:25:45] [INFO ] Starting X server on display 10: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log  
[20230221-09:25:45] [DEBUG] Calling exec (excutable: /usr/lib/xorg/Xorg, arguments: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log)
[20230221-09:25:45] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20230221-09:25:45] [INFO ] Session started successfully for user user.name on display 10
[20230221-09:25:45] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20230221-09:25:45] [INFO ] Session in progress on display 10, waiting until the window manager (pid 1181) exits to end the session
[20230221-09:25:45] [DEBUG] waiting for pid 1181 to exit
[20230221-09:25:45] [INFO ] Found X server running at /tmp/.X11-unix/X10
[20230221-09:25:45] [DEBUG] The user session on display 10 did not request a specific window manager
[20230221-09:25:45] [DEBUG] The user home directory window manager configuration is enabled but window manager program does not exist: /home/user.name/startwm.sh
[20230221-09:25:45] [INFO ] Starting the xrdp channel server for display 10
[20230221-09:25:45] [INFO ] Starting the default window manager on display 10: /etc/xrdp/startwm.sh
[20230221-09:25:45] [DEBUG] Calling exec (excutable: /etc/xrdp/startwm.sh, arguments: /etc/xrdp/startwm.sh )
[20230221-09:25:45] [DEBUG] Calling exec (excutable: /usr/sbin/xrdp-chansrv, arguments: /usr/sbin/xrdp-chansrv)
[20230221-09:25:45] [WARN ] Window manager (pid 1181, display 10) exited with non-zero exit code 2 and signal 0. This could indicate a window manager config problem
[20230221-09:25:45] [WARN ] Window manager (pid 1181, display 10) exited quickly (0 secs). This could indicate a window manager config problem
[20230221-09:25:45] [INFO ] Calling auth_stop_session and auth_end from pid 1168
[20230221-09:25:45] [INFO ] Terminating X server (pid 1182) on display 10
[20230221-09:25:45] [INFO ] Terminating the xrdp channel server (pid 1200) on display 10
[20230221-09:25:45] [DEBUG] waiting for pid 1182 to exit
[20230221-09:25:46] [INFO ] X server on display 10 (pid 1182) returned exit code 0 and signal number 0
[20230221-09:25:46] [DEBUG] waiting for pid 1200 to exit
[20230221-09:25:46] [INFO ] xrdp channel server for display 10 (pid 1200) exit code 0 and signal number 0
[20230221-09:25:46] [INFO ] cleanup_sockets:
[20230221-09:25:46] [DEBUG] cleanup_sockets: deleting /run/xrdp/sockdir/xrdpapi_10
[20230221-09:25:46] [INFO ] ++ terminated session:  username user.name, display :10.0, session_pid 1168, ip 10.50.1.112:57836 - socket: 12

The fact that the apt update was what triggered this issue is a hunch, but everything was working fine prior to 20 February.

excerpt from /var/log/apt/history.log

Start-Date: 2023-02-20  00:26:22
Commandline: /usr/bin/apt-get -y -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold upgrade --with-new-pkgs
Requested-By: ubuntu (1000)
Upgrade: python3-distupgrade:amd64 (1:22.04.15, 1:22.04.16), ubuntu-release-upgrader-gtk:amd64 (1:22.04.15, 1:22.04.16), ubuntu-advantage-desktop-daemon:amd64 (1.9~22.04.1, 1.10~22.04.1), squid:amd64 (5.2-1ubuntu4.2, 5.2-1ubuntu4.3), python-apt-common:amd64 (2.4.0, 2.4.0ubuntu1), squid-common:amd64 (5.2-1ubuntu4.2, 5.2-1ubuntu4.3), motd-news-config:amd64 (12ubuntu4.2, 12ubuntu4.3), fwupd-signed:amd64 (1.44+1.2-3, 1.51~22.04.1+1.2-3ubuntu0.2), update-notifier:amd64 (3.192.54, 3.192.54.5), base-files:amd64 (12ubuntu4.2, 12ubuntu4.3), python3-apt:amd64 (2.4.0, 2.4.0ubuntu1), ubuntu-release-upgrader-core:amd64 (1:22.04.15, 1:22.04.16), ubuntu-advantage-tools:amd64 (27.12~22.04.1, 27.13.5~22.04.1), update-notifier-common:amd64 (3.192.54, 3.192.54.5)
End-Date: 2023-02-20  00:27:16

What I also did notice that removing the below code from startwm.sh...

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

... would enable me to be able to log in. But I then get some GNOME related error messages on the display, and some unexpected behaviour like the keyring/auth related errors when using tableplus for example.

Do let me know if there is any more information I can provide.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions