I had xrdp+gnome working no problem with 22 and 24. I’ve upgraded a machine to 26.04 resolute raccoon and am having great difficulty getting it to work. I’ve tried switching xcfe but get the exact same behavior.
Using the standard Windows RDP client, I can reach the machine, and it shows the standard xrdp log in screen where I enter “Xorg”, username and password. Authentication takes place but I’m left with blank, blue screen. After a minute or two a Connection Log message will pop-up
All logs seem fine except for xrdp-sesman.log. Here is that log
[2025-10-19T13:11:49.945-0400] [INFO ] Starting the xrdp channel server for display :11
[2025-10-19T13:11:49.946-0400] [INFO ] Using window manager on display 11 from user home directory: /home/username/startwm.sh
[2025-10-19T13:11:49.950-0400] [INFO ] Session in progress on display :11. Waiting until the window manager (pid 2406054) exits to end the session
[2025-10-19T13:11:49.960-0400] [WARN ] Window manager (pid 2406054, display 11) exited with non-zero exit code 2. This could indicate a window manager config problem
[2025-10-19T13:11:49.967-0400] [WARN ] Window manager (pid 2406054, display 11) exited quickly (0 secs). This could indicate a window manager config problem
[2025-10-19T13:11:49.976-0400] [INFO ] Terminating X server (pid 2406045) on display :11
[2025-10-19T13:11:49.984-0400] [INFO ] Terminating the xrdp channel server (pid 2406055) on display :11
[2025-10-19T13:11:49.992-0400] [INFO ] X server pid 2406045 on display :11 finished
[2025-10-19T13:11:49.997-0400] [INFO ] xrdp channel server pid 2406055 on display :11 finished
[2025-10-19T13:11:50.158-0400] [INFO ] Session on display 11 has finished.
xrdp.log looks fine
[2025-10-19T13:11:40.801-0400] [INFO ] xrdp_mm_egfx_invalidate_wm_screen:
[2025-10-19T13:11:40.805-0400] [INFO ] xrdp_mm_egfx_caps_advertise: egfx created.
[2025-10-19T13:11:48.846-0400] [WARN ] Ignoring obsolete SCP port value '3350'
[2025-10-19T13:11:48.854-0400] [INFO ] xrdp_wm_log_msg: sesman connect ok
[2025-10-19T13:11:48.859-0400] [INFO ] xrdp_wm_log_msg: Performing login request for username
[2025-10-19T13:11:48.900-0400] [INFO ] xrdp_wm_log_msg: login was successful - creating session
[2025-10-19T13:11:49.958-0400] [INFO ] xrdp_wm_log_msg: session is available on display 11 for user username
[2025-10-19T13:11:49.963-0400] [INFO ] xrdp_wm_log_msg: Connecting to session
[2025-10-19T13:11:49.972-0400] [INFO ] loaded module 'libxup.so' ok, interface size 10416, version 4
[2025-10-19T13:11:49.980-0400] [INFO ] lib_mod_connect: connecting via UNIX socket
#!/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
if test -r ~/.profile; then
. ~/.profile
fi
test -x /etc/X11/Xsession && exec /etc/X11/Xsession
exec /bin/sh /etc/X11/Xsession
For a bug report to be useful or a regression, we need to know if it worked in the last stable release, ie. Ubuntu 25.10 (questing) but you gave no details about that?
If you’re reporting a bug; you’re on the wrong place, and this isn’t a valid area for support.
The resolute release is also extremely early alpha and very little change has occurred since questing or Ubuntu 25.10.
My apologies. I know I’m not supposed to post requests for help on non-supported versions in the normal help sub-forum. I thought it would be OK to ask for help on pre-release versions here.
Is there any mechanism for requesting help with a pre-release version?
This site/area really only makes sense (at least to me) if there is a difference between Ubuntu 25.10 which is supported in the support area of this site, and the resolute system you indicate you’re using (I’m using right now myself actually), but you don’t indicate that you even explored it on questing (25.10); specifying only much older releases.
To be useful detail here for discussion, it has to relate to change made in the resolute repository over the latest stable release which is questing, which should be somewhat easy to track down given there are so few changes currently.
The #ubuntu-next area of IRC is one area, as the topic for it states
Topic for #ubuntu-next is: Welcome to the support channel for pre-release versions of Ubuntu. Beware these are unstable and will probably break your computer | Current dev version: Resolute Raccoon (26.04 LTS) | Schedule: https://ubottu.com/y/rr | Testing: Testing tracker | Ubuntu QA (Downloading often? See https://ubottu.com/y/zsync) | For support of released versions, see ubuntu
This post hasn’t been closed, so you may get a response, but as support is NOT the purpose of this area, and its so early in the development cycle, you may not get much discussion here either.
For those who might see this in their search results, it appears that with X11 support being dropped for Wayland as of 25.xx, that’s why it doesn’t work with 26.04.
So the question is, how to support Gnome remote on a headless server?
If you try it on Ubuntu 25.04 I’m certain it’ll work, as that uses a GNOME 48 which has full Xorg/X11 support (as with prior releases of GNOME)
Xorg/X11 support wasn’t removed from GNOME until GNOME 49, which is the version used in Ubuntu 25.10.
Future releases (inc. Ubuntu 26.04) will have newer versions of GNOME, and your issues relates to the desktop (which is why it works in Xfce using Xorg/X11 on 25.10 & current resolute/26.04). Ubuntu still has support for Xorg/X11 in all releases.
Yes, but it would appear that Gnome is no longer going to support Xorg/X11. Is there a path forward for remote Gnome via xrdp?
In the meantime, as you have noted, I have rebuilt my machine with 25.10, added task-xfce-desktop, and after the usual fussing over a number of additional settings and config’s, that combination is working quite well.
That is up to the GNOME project. I’m only an occasional user of GNOME, and have no special knowledge of where they’re going, but the removal of the Xorg/X11 code in GNOME 49 did not look temporary.
