xrdp with egfx pipeline testrun

[akarl10]

#1422 tracks the progress of the addition the new gfx pipeline.

news for ubuntu 24.04

since now most of this is upstream, I built a package based on devel for ubuntu 24.04. This package has software h264 only and no specific nvidia support. If you need that, it seems the 23.04 version still works under 24.04.

nvidia support is back again after being disabled for some time because of serve issues (to be exact starting with package version 1:0.10.80-20250813-1ubuntu1+0egfx2). It should enable automatically on new installations. For hardware H264 encoding enable the session variable XRDP_USE_ACCEL_ASSIST=1 in the [SessionVariables] section in sesman.ini

A remaining issue with nvidia/lrandr and the plasma desktop is that the desktop does not resize to the real size, altough the windows itself can move everywhere.

In doubt apt purge xrdp-egfx xorgxrdp-egfx, remove /etc/xrdp, /etc/X11/xrdp and reinstall both packages.

when upgrading check if /etc/xrdp/sesman.ini contains SessionSockdirGroup=xrdp in the [Security] section

Even though the pulseaudio module is still provided, pipewire-module-xrdp should be used instead

original post

This is a huge undertaking that has mostly be done by only two developers. @Nexarian is currently preparing merge requests, step by step, but this will take some time. @jsorg71 has done most of the groundwork.

I made some experiments for myself and to make it easer to test it on different platforms (intel gpu, amd gpu, nvidia gpu, virgl) I made a ubuntu ppa. This is still a moving target, but if someone wants to try out what xrdp will feel like in the (hopefully near) future here is my own instruction for my test setup

egfx xrdp installation

The patched version uses another name to prevent conflicts with the ubuntu version of xrdp
you may switch between them by uninstalling xrdp and installing xrdp-egfx.

Currently for jammy and kinetic only. Based on https://github.com/Nexarian/xrdp/commits/mainline_merge and https://github.com/Nexarian/xorgxrdp/commits/mainline_merge

all commands are running in a root session. In doubt simply put a sudo in front of every line or start a root shell with
sudo -i or sudo -s (what you prefer)

clean install

apt-add-repository ppa:saxl/xrdp-egfx
apt install xrdp-egfx xorgxrdp-egfx
#optional
apt install pulseaudio-module-xrdp

I higly recommend replacing configuration files with the new provided ones if asked.

You should reboot now since a udev rule is added that allows anyone to use /dev/dri/renderD*. This is needed for non-nvidia 3d accelleration

The specific file is /usr/lib/udev/rules.d/90-xorgxrdp-dri.rules

Also xorgxrdp-egfx has a postinstall script that reconfigures sesman.ini for nvidia gpu if needed. Consequiently a restart of that service might be needed.

swap from xrdp to xrdp-egfx

apt purge xrdp xorgxrdp
apt-add-repository ppa:saxl/xrdp-egfx
apt install xrdp-egfx xorgxrdp-egfx
#optional
apt install pulseaudio-module-xrdp

swap back to xrdp from xrdp-egfx

apt purge xrdp-egfx xorgxrdp-egfx
apt install xrdp xorgxrdp

#optional
rm /etc/apt/sources.list.d/saxl-ubuntu-xrdp-egfx*.list
rm /etc/apt/trusted.gpg.d/saxl-ubuntu-xrdp-egfx.gpg*
apt remove pulseaudio-module-xrdp

tweaks

desktop selection

The desktop that gets launched is configured in /etc/xrdp/sesman.ini
Look for the line

DESKTOP_SESSION=

you can put every desktop listed in /usr/share/xsessions. Just put the name wihout .desktop
If you want to use this feature on a per user basis you could put something like

[ -n "$XRDP_SESSION" ] && export DESKTOP_SESSION=cinnamon2d

in ~/.profile

nvidia h264 hardware encoding

if you have a nvidia gpu you might enable hardware h264 encoding by editing
/etc/xrdp/sesman.ini

simply change the line at the near bottom from
# XRDP_USE_HELPER=1 to XRDP_USE_HELPER=1

multisession support and more consistent pulseaudio

you might try enabling multisession support. This way reduces possible conflicts if you somehow are logged in twice or more (ex. locally and via xrdp)
Currently to get audio in Ubuntu Kinetic you need this (or at least it is the easies way)

Essentially this makes a "subsession" in /run/user/UID/, spawns a matching dbus, pulseaudio and pipewire (that uses pulseaudio)

simply change the line at the near bottom of /etc/xrdp/sesman.ini from
# XRDP_USE_MULTISESSION=1 to XRDP_USE_MULTISESSION=1

Should work with both plasma and gnome.

check out https://github.com/matt335672/nest-systemd-user

verify that it's working

gfx pipeline

You should immediatly see a big performance improvement when connecting with a modern rdp client.
mstsc should connect with gfx h264 while stock freerdp in ubuntu repositories only uses gfx rfx progressive

what codec is used you will see in /var/log/xrdp.log. Look for a line that says

rdp_encoder_create: starting gfx rfx pro codec session

or

xrdp_encoder_create: starting h264 codec session gfx

desktop 3d and video

For 3d check if glxinfo | grep renderer outputs your gpu. In a plasma desktop session your taskbar's background should be transparent with a blur effect.

For video check the output of vainfo.

Note that ubuntu jammy's version of libva2 has a issue with intel gpu's that has been fixed since in kinetic (see intel/libva#582). As a workaround you might set an appropriate LIBVA_DRIVER_NAME= in /etc/xrdp/sesman.ini in the [SessionVariables] section.

client side considerations

to get h264 in freerdp you must recompile it with ffmpeg enabled (ubuntu has disabled it because ffmpeg is not in main).

you should also get better performance when connecting to a windows rdp server

other changes from ubuntu xrdp

startwm.sh

changed if x-session-manager is gnome-session and start with the correct environment so that the ubuntu shell is started instead of the default gnome one

some modifications for my own XRDP_USE_MULTISESSION idea

polkit

a polkit (/etc/polkit-1/localauthority/10-vendor.d/01-xrdp-rules.pkla) rule is added. This prevents popups for network and color management

issues

nvidia uses lrandr since standard randr will not work there. This one is incomplete and for plasma this means the desktop shell does not respond to size changes. At least it shows the correct output in xrandr

the gfx rfx pro codec makes a "scanline" effect.

snap does not work fully in XRDP_USE_MULTISESSION mode (mainly sound and maybe open file dialog issues)
flatpak works tough

[senposage]

this greatly reduces cpu usage under WSL
playing youtube went from 70%+ utilisation to 20%
thanks

[goroption]

Hi
i'm switched from already working xrdp to xrdp-egfx, and have an issue
when i'm try to connect, mstsc abort connection by "protocol error"
in /var/log/xrdp.log have few error

[2023-02-17T14:38:26.602+0300] [INFO ] TLS connection established from [::ffff:10.143.1.27]:9298 TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384
[2023-02-17T14:38:26.908+0300] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[2023-02-17T14:38:26.915+0300] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 5242880 MB cache entries 100
[2023-02-17T14:38:26.922+0300] [INFO ] xrdp_caps_process_codecs: NSCodec(CA8D1BB9-000F-154F-589F-AE2D1A87E2D6), codec id [1], properties len [3]
[2023-02-17T14:38:26.925+0300] [WARN ] xrdp_caps_process_codecs: unknown(2744CCD4-9D8A-4E74-803C-0ECBEEA19C54), codec id [5], properties len [49]
[2023-02-17T14:38:26.928+0300] [INFO ] xrdp_caps_process_codecs: RemoteFX(76772F12-BD72-4463-AFB3-B73C9C6F7886), codec id [3], properties len [49]
[2023-02-17T14:38:26.935+0300] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[2023-02-17T14:38:26.943+0300] [WARN ] local keymap file for 0x00000409 found and doesn't match built in keymap, using local keymap file
[2023-02-17T14:38:26.945+0300] [INFO ] Login screen monitor height is 1080 pixels over 194 mm (141 DPI)
[2023-02-17T14:38:27.106+0300] [INFO ] xrdp_egfx_create: error 0 channel_id 1
[2023-02-17T14:38:27.207+0300] [INFO ] xrdp_mm_egfx_caps_advertise:
[2023-02-17T14:38:27.211+0300] [INFO ] version 0x00080004 flags 0x00000000 (index: 0)
[2023-02-17T14:38:27.213+0300] [INFO ] version 0x00080105 flags 0x00000000 (index: 1)
[2023-02-17T14:38:27.216+0300] [INFO ] version 0x000a0002 flags 0x00000000 (index: 2)
[2023-02-17T14:38:27.219+0300] [INFO ] version 0x000a0200 flags 0x00000000 (index: 3)
[2023-02-17T14:38:27.222+0300] [INFO ] version 0x000a0301 flags 0x00000000 (index: 4)
[2023-02-17T14:38:27.228+0300] [INFO ] version 0x000a0400 flags 0x00000000 (index: 5)
[2023-02-17T14:38:27.233+0300] [INFO ] version 0x000a0502 flags 0x00000000 (index: 6)
[2023-02-17T14:38:27.242+0300] [INFO ] version 0x000a0600 flags 0x00000000 (index: 7)
[2023-02-17T14:38:27.245+0300] [INFO ] replying version 0x000a0600 flags 0x00000000
[2023-02-17T14:38:27.252+0300] [INFO ] xrdp_mm_egfx_caps_advertise: xrdp_egfx_send_capsconfirm error 0
[2023-02-17T14:38:27.256+0300] [INFO ] xrdp_egfx_send_reset_graphics:
[2023-02-17T14:38:27.264+0300] [INFO ] xrdp_egfx_send_reset_graphics: width 1920 height 1080 monitorcount 1
[2023-02-17T14:38:27.267+0300] [INFO ] xrdp_egfx_send_reset_graphics: xrdp_egfx_send_data error 0
[2023-02-17T14:38:27.272+0300] [INFO ] xrdp_mm_egfx_caps_advertise: xrdp_egfx_send_reset_graphics error 0 monitorCount 0
[2023-02-17T14:38:27.275+0300] [INFO ] xrdp_encoder_create:
[2023-02-17T14:38:27.277+0300] [INFO ] xrdp_mm_egfx_invalidate_all:
[2023-02-17T14:38:27.281+0300] [INFO ] xrdp_mm_egfx_caps_advertise: egfx created.
[2023-02-17T14:38:27.382+0300] [ERROR] SSL_write: I/O error
[2023-02-17T14:38:27.386+0300] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[2023-02-17T14:38:27.390+0300] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[2023-02-17T14:38:27.395+0300] [ERROR] Attempting to send data to a channel that is not open. channel id 1, channel status CLOSED

im think SSL_write: I/O error is a main problem, i'm trying to search this error, but don't find working solution

[2023-02-17T14:38:27.382+0300] [ERROR] SSL_write: I/O error
[2023-02-17T14:38:27.386+0300] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[2023-02-17T14:38:27.390+0300] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed

if you catch this error and have a solution, tell me please

[akarl10]

SSL_write: I/O error could also simply be the client (mstsc) disconnecting
what is strange is that after xrdp_encoder_create: there is no starting h264 codec session or something like that

have you restarted xrdp or the machine after switching from xrdp to xrdp-egfx?

do you have another client you could test with?

[akarl10]

ok, found the issue... you must set the color depth to 32 in mstsc.

[goroption]

in mstsc....wow...its really fix that!
before this error im trying to change color depth on server side, to 24 and lower...

right now its works, thank you so much!
takin it to testing)

[akarl10]

this issue is now fixed in my ppa. I also notified someone on gitter, so I think they will work out a appropriate solution.
Note that this setting has no meaning for a server that supports egfx. This setting is only for old non gfx servers

[philstopford]

I am having some issues with this that I don't really understand :

[2023-02-18T13:01:37.859-0600] [INFO ] dynamic_monitor_process_queue: Clearing completed resize (w: 2050 x h: 1221). It took 1230 milliseconds.
[2023-02-18T13:02:18.118-0600] [INFO ] Received termination signal, stopping the server accept new connections thread
[2023-02-18T13:02:19.148-0600] [ERROR] Attempting to send data to a channel that is not open. channel id 1, channel status CLOSED
[2023-02-18T13:02:19.404-0600] [INFO ] address [0.0.0.0] port [3389] mode 1
[2023-02-18T13:02:19.407-0600] [INFO ] listening to port 3389 on 0.0.0.0
[2023-02-18T13:02:19.417-0600] [INFO ] xrdp_listen_pp done
[2023-02-18T13:02:21.421-0600] [INFO ] starting xrdp with pid 5651
[2023-02-18T13:02:21.488-0600] [INFO ] address [0.0.0.0] port [3389] mode 1
[2023-02-18T13:02:21.491-0600] [INFO ] listening to port 3389 on 0.0.0.0
[2023-02-18T13:02:21.493-0600] [INFO ] xrdp_listen_pp done
[2023-02-18T13:02:30.909-0600] [INFO ] Socket 12: connection accepted from [::ffff:192.168.4.32]:54462
[2023-02-18T13:02:30.976-0600] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[2023-02-18T13:02:30.979-0600] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[2023-02-18T13:02:30.982-0600] [INFO ] Security protocol: configured [SSL|RDP], requested [SSL|HYBRID|RDP], selected [SSL]
[2023-02-18T13:02:30.992-0600] [INFO ] Connected client computer name: darkwing
[2023-02-18T13:02:30.995-0600] [WARN ] Physical desktop dimensions (0x0) are invalid
[2023-02-18T13:02:30.998-0600] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[2023-02-18T13:02:31.893-0600] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[2023-02-18T13:02:31.693-0600] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00000409]
[2023-02-18T13:02:31.759-0600] [ERROR] xrdp_load_keyboard_layout: error opening /etc/xrdp/xrdp_keyboard.ini
[2023-02-18T13:02:31.762-0600] [INFO ] TLS connection established from [::ffff:192.168.4.32]:54462 TLSv1.3 with cipher TLS_AES_256_GCM_SHA384
[2023-02-18T13:02:31.994-0600] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[2023-02-18T13:02:32.605-0600] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 7864320 MB cache entries 2000
[2023-02-18T13:02:32.635-0600] [INFO ] xrdp_caps_process_codecs: RemoteFX(76772F12-BD72-4463-AFB3-B73C9C6F7886), codec id [3], properties len [49]
[2023-02-18T13:02:32.664-0600] [WARN ] Client Capability: not enough orders supported by client, client wants off screen bitmap but offscreen bitmaps disabled
[2023-02-18T13:02:32.717-0600] [WARN ] Cannot find keymap file /etc/xrdp/km-00000409.ini
[2023-02-18T13:02:32.748-0600] [WARN ] Cannot find keymap file /etc/xrdp/km-00000409.ini
[2023-02-18T13:02:32.778-0600] [WARN ] File does not exist: /etc/xrdp/km-00000409.ini
[2023-02-18T13:02:32.805-0600] [WARN ] No information is available to determine login screen DPI
[2023-02-18T13:02:32.830-0600] [WARN ] No DPI value is available to find login font
[2023-02-18T13:02:32.858-0600] [WARN ] Using the default_dpi of 96
[2023-02-18T13:02:32.145-0600] [INFO ] xrdp_egfx_create: error 0 channel_id 1
[2023-02-18T13:02:32.148-0600] [INFO ] xrdp_mm_egfx_caps_advertise:
[2023-02-18T13:02:32.149-0600] [INFO ]   version 0x00080004 flags 0x00000001 (index: 0)
[2023-02-18T13:02:32.151-0600] [INFO ]   version 0x00080105 flags 0x00000001 (index: 1)
[2023-02-18T13:02:32.152-0600] [INFO ]   version 0x000a0002 flags 0x00000020 (index: 2)
[2023-02-18T13:02:32.153-0600] [INFO ]   version 0x000a0200 flags 0x00000020 (index: 3)
[2023-02-18T13:02:32.154-0600] [INFO ]   version 0x000a0301 flags 0x00000020 (index: 4)
[2023-02-18T13:02:32.156-0600] [INFO ]   version 0x000a0400 flags 0x00000020 (index: 5)
[2023-02-18T13:02:32.157-0600] [INFO ]   version 0x000a0502 flags 0x00000020 (index: 6)
[2023-02-18T13:02:32.159-0600] [INFO ]   version 0x000a0600 flags 0x00000020 (index: 7)
[2023-02-18T13:02:32.160-0600] [INFO ]   replying version 0x000a0600 flags 0x00000020
[2023-02-18T13:02:32.161-0600] [INFO ] xrdp_mm_egfx_caps_advertise: xrdp_egfx_send_capsconfirm error 0
[2023-02-18T13:02:32.162-0600] [INFO ] xrdp_egfx_reset_graphics:
[2023-02-18T13:02:32.164-0600] [INFO ] xrdp_egfx_reset_graphics: width 2048 height 1220 monitorcount 1
[2023-02-18T13:02:32.165-0600] [INFO ] xrdp_mm_egfx_caps_advertise: xrdp_egfx_send_reset_graphics error 0 monitorCount 0
[2023-02-18T13:02:32.167-0600] [INFO ] xrdp_encoder_create:
[2023-02-18T13:02:32.169-0600] [INFO ] xrdp_encoder_create: starting gfx rfx pro codec session
[2023-02-18T13:02:32.172-0600] [INFO ] xrdp_mm_egfx_invalidate_all:
[2023-02-18T13:02:32.174-0600] [INFO ] xrdp_mm_egfx_caps_advertise: egfx created.
[2023-02-18T13:02:32.177-0600] [WARN ] Ignoring obsolete SCP port value '3350'
[2023-02-18T13:02:32.179-0600] [INFO ] xrdp_wm_log_msg: sesman connect ok
[2023-02-18T13:02:32.190-0600] [INFO ] xrdp_wm_log_msg: Performing login request for phil
[2023-02-18T13:02:32.224-0600] [INFO ] xrdp_wm_log_msg: login was successful - creating session
[2023-02-18T13:02:32.231-0600] [INFO ] xrdp_wm_log_msg: session is available on display 11 for user phil
[2023-02-18T13:02:32.232-0600] [INFO ] xrdp_wm_log_msg: Connecting to session
[2023-02-18T13:02:32.233-0600] [INFO ] loaded module 'libxup.so' ok, interface size 10408, version 4
[2023-02-18T13:02:32.234-0600] [INFO ] lib_mod_connect: connecting via UNIX socket
[2023-02-18T13:02:34.236-0600] [INFO ] lib_mod_log_peer: xrdp_pid=5655 connected to Xorg_pid=5660 Xorg_uid=1000 Xorg_gid=1000 client=[::ffff:192.168.4.32]:54462
[2023-02-18T13:02:34.302-0600] [INFO ] xrdp_wm_log_msg: Connecting to chansrv
[2023-02-18T13:02:34.305-0600] [WARN ] sanitise_extended_monitor_attributes: physical_width is not within valid range. Setting physical_width to 0mm, Setting physical_height to 0mm, physical_width was: 0
[2023-02-18T13:02:34.308-0600] [WARN ] sanitise_extended_monitor_attributes: physical_height is not within valid range. Setting physical_width to 0mm, Setting physical_height to 0mm, physical_height was: 0
[2023-02-18T13:02:34.310-0600] [WARN ] sanitise_extended_monitor_attributes: desktop_scale_factor is not within valid range of [100, 500]. Assuming 100. Value was: 0
[2023-02-18T13:02:34.313-0600] [WARN ] sanitise_extended_monitor_attributes: device_scale_factor a valid value (One of 100, 140, 180). Assuming 100. Value was: 0
[2023-02-18T13:02:34.315-0600] [INFO ] Received memory_allocation_completecommand. width: 2048, height: 1280
[2023-02-18T13:02:34.318-0600] [INFO ] server_reset:
[2023-02-18T13:02:34.320-0600] [INFO ] proc_enc_msg: xrdp_mm term
[2023-02-18T13:02:35.331-0600] [INFO ] Received memory_allocation_completecommand. width: 2112, height: 1280
[2023-02-18T13:02:35.340-0600] [INFO ] server_reset:
[2023-02-18T13:02:35.343-0600] [INFO ] server_reset: Advancing server monitor resized.
[2023-02-18T13:02:35.349-0600] [INFO ] xrdp_egfx_create: error 0 channel_id 1
[2023-02-18T13:02:35.352-0600] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[2023-02-18T13:02:35.355-0600] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 7864320 MB cache entries 2000
[2023-02-18T13:02:35.357-0600] [INFO ] xrdp_caps_process_codecs: RemoteFX(76772F12-BD72-4463-AFB3-B73C9C6F7886), codec id [3], properties len [49]
[2023-02-18T13:02:35.360-0600] [WARN ] Client Capability: not enough orders supported by client, client wants off screen bitmap but offscreen bitmaps disabled
[2023-02-18T13:02:35.449-0600] [INFO ] xrdp_mm_egfx_caps_advertise:
[2023-02-18T13:02:35.451-0600] [INFO ]   version 0x00080004 flags 0x00000001 (index: 0)
[2023-02-18T13:02:35.452-0600] [INFO ]   version 0x00080105 flags 0x00000001 (index: 1)
[2023-02-18T13:02:35.453-0600] [INFO ]   version 0x000a0002 flags 0x00000020 (index: 2)
[2023-02-18T13:02:35.454-0600] [INFO ]   version 0x000a0200 flags 0x00000020 (index: 3)
[2023-02-18T13:02:35.455-0600] [INFO ]   version 0x000a0301 flags 0x00000020 (index: 4)
[2023-02-18T13:02:35.456-0600] [INFO ]   version 0x000a0400 flags 0x00000020 (index: 5)
[2023-02-18T13:02:35.457-0600] [INFO ]   version 0x000a0502 flags 0x00000020 (index: 6)
[2023-02-18T13:02:35.458-0600] [INFO ]   version 0x000a0600 flags 0x00000020 (index: 7)
[2023-02-18T13:02:35.459-0600] [INFO ]   replying version 0x000a0600 flags 0x00000020
[2023-02-18T13:02:35.460-0600] [INFO ] xrdp_mm_egfx_caps_advertise: xrdp_egfx_send_capsconfirm error 0
[2023-02-18T13:02:35.461-0600] [INFO ] xrdp_egfx_reset_graphics:
[2023-02-18T13:02:35.462-0600] [INFO ] xrdp_egfx_reset_graphics: (index 0) monitor left 0 top 0 right 2049 bottom 1220 is_primary 1
[2023-02-18T13:02:35.463-0600] [INFO ] xrdp_egfx_reset_graphics: width 2050 height 1221 monitorcount 1
[2023-02-18T13:02:35.464-0600] [INFO ] xrdp_mm_egfx_caps_advertise: xrdp_egfx_send_reset_graphics error 0 monitorCount 1
[2023-02-18T13:02:35.465-0600] [INFO ] xrdp_encoder_create:
[2023-02-18T13:02:35.466-0600] [INFO ] xrdp_encoder_create: starting gfx rfx pro codec session
[2023-02-18T13:02:35.467-0600] [INFO ] xrdp_mm_egfx_invalidate_all:
[2023-02-18T13:02:35.468-0600] [INFO ] xrdp_mm_egfx_caps_advertise: egfx created.
[2023-02-18T13:02:35.486-0600] [INFO ] dynamic_monitor_process_queue: Clearing completed resize (w: 2050 x h: 1221). It took 1166 milliseconds.

I'm trying to connect with Remmina, in case that matters. The client just gets a black screen.

[akarl10]

The script breaks when it tries to install cuda due to version mismatches in the apt repositories:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 cuda-drivers-525 : Depends: libnvidia-common-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
                    Depends: libnvidia-compute-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
                    Depends: libnvidia-decode-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
                    Depends: libnvidia-encode-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
                    Depends: libnvidia-fbc1-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
                    Depends: libnvidia-gl-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
                    Depends: nvidia-compute-utils-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
                    Depends: nvidia-dkms-525 (>= 525.85.12)
                    Depends: nvidia-driver-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
                    Depends: nvidia-kernel-common-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
                    Depends: nvidia-kernel-source-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed or
                             nvidia-kernel-open-525 (>= 525.85.12) but it is not going to be installed
                    Depends: nvidia-utils-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
                    Depends: xserver-xorg-video-nvidia-525 (>= 525.85.12) but 525.85.05-1pop0~1675115257~22.04~ad22b1f is to be installed
E: Unable to correct problems, you have held broken packages.

Are these specific cuda drivers needed?

I don't know.. This ppa is compiled without cuda

Also, the script attempts to remove dbus-user-session which will apparently break the system:

The following packages have unmet dependencies:
 pop-desktop : Depends: dbus-user-session
               Recommends: libreoffice-calc but it is not going to be installed
               Recommends: libreoffice-impress but it is not going to be installed
               Recommends: libreoffice-writer but it is not going to be installed
               Recommends: libreoffice-gnome but it is not going to be installed
               Recommends: libreoffice-ogltrans
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

i think removing dbus-user-session is not required. Afaik this is only done because of #2491, but if you just start one session per user it should work regardless (else you probably get another black sceen)

To run the script version, I went to purge the egfx packages. It seems that there might be issues in the packages :

Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  xorgxrdp-egfx* xrdp-egfx*
0 upgraded, 0 newly installed, 2 to remove and 1 not upgraded.
After this operation, 4,605 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 211374 files and directories currently installed.)
Removing xorgxrdp-egfx (1:0.9.19.20221128-1ubuntu1+0egfx1~jammy) ...
Removing xrdp-egfx (0.9.19.20230215-1ubuntu1+0egfx12~jammy) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
(Reading database ... 211274 files and directories currently installed.)
Purging configuration files for xrdp-egfx (0.9.19.20230215-1ubuntu1+0egfx12~jammy) ...
setfacl: Option -x: Invalid argument near character 3
Purging configuration files for xorgxrdp-egfx (1:0.9.19.20221128-1ubuntu1+0egfx1~jammy) ...
rm: cannot remove '/etc/X11/xrdp': Is a directory
dpkg: error processing package xorgxrdp-egfx (--purge):
 installed xorgxrdp-egfx package post-removal script subprocess returned error exit status 1
Errors were encountered while processing:
 xorgxrdp-egfx
E: Sub-process /usr/bin/dpkg returned an error code (1)

sorry about that. if you manually rm -rf /etc/X11/xrdp the deinstallation should continue..

[philstopford]

Also tried with a Xubuntu 22.04.1 install, updated. That seems to give the same kind of results. Logs attached.
xrdp.log
xrdp-sesman.log

[akarl10]

Also tried with a Xubuntu 22.04.1 install, updated. That seems to give the same kind of results. Logs attached. xrdp.log xrdp-sesman.log

this time the error is different. Xorg does not start. see ~/.xorgxrdp.10.log

[philstopford]

Yes, I also tried with the script (which runs fine under Xubuntu - no CUDA or dbus complaints). That also yields a blackscreen just like the packages. Logs from the script attached.
script_xorgxrdp.10.log
script_xsession-errors.log
xrdp-sesman.log
xrdp.log

[akarl10]

hmm, maybe the nvidia driver itself has a issue..
if "upstream merge" does not work I suppose it is better getting in contact with @Nexarian

p.s. I updated the documentation of my package and described how to select the preferred desktop. A update should be available that makes custom .xsession run again

[howudodat]

Not sure if I did this right, but it's still really slow for me
Install log:

root@xrdp2:~# history
    1  sudo apt update
    2  apt -y upgrade
    3  apt -y install htop mlocate qemu-guest-agent 
    4  apt install kubuntu-desktop 
    5  apt-add-repository ppa:saxl/xrdp-egfx
    6  apt install xrdp-egfx xorgxrdp-egfx

I connect with remmina and I can watch it paint the screen line by line (connected via 10Mbps connection)
I dont see gfx in the log:

[2023-02-24T19:35:42.639+0000] [INFO ] Socket 12: connection accepted from [::ffff:10.9.0.3]:8947
[2023-02-24T19:35:42.643+0000] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[2023-02-24T19:35:42.645+0000] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[2023-02-24T19:35:42.647+0000] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[2023-02-24T19:35:42.661+0000] [WARN ] Cannot accept TLS connections because certificate or private key file is not readable. certificate file: [/etc/xrdp/cert.pem], private key file: [/etc/xrdp/key.pem]
[2023-02-24T19:35:42.662+0000] [INFO ] Security protocol: configured [RDP], requested [SSL|HYBRID|RDP], selected [RDP]
[2023-02-24T19:35:42.835+0000] [INFO ] Connected client computer name: laptop
[2023-02-24T19:35:42.836+0000] [WARN ] Physical desktop dimensions (0x0) are invalid
[2023-02-24T19:35:42.837+0000] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[2023-02-24T19:35:42.839+0000] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[2023-02-24T19:35:43.658+0000] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00000409]
[2023-02-24T19:35:43.675+0000] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [us] options []
[2023-02-24T19:35:43.688+0000] [INFO ] Non-TLS connection established from [::ffff:10.9.0.3]:8947 with security level : high
[2023-02-24T19:35:45.440+0000] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[2023-02-24T19:35:45.469+0000] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 7864320 MB cache entries 2000
[2023-02-24T19:35:45.481+0000] [WARN ] Client Capability: not enough orders supported by client, client wants off screen bitmap but offscreen bitmaps disabled
[2023-02-24T19:35:45.598+0000] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[2023-02-24T19:35:45.625+0000] [WARN ] local keymap file for 0x00000409 found and doesn't match built in keymap, using local keymap file
[2023-02-24T19:35:45.659+0000] [WARN ] No information is available to determine login screen DPI
[2023-02-24T19:35:45.671+0000] [WARN ] No DPI value is available to find login font
[2023-02-24T19:35:45.684+0000] [WARN ] Using the default_dpi of 96
[2023-02-24T19:35:45.845+0000] [WARN ] Ignoring obsolete SCP port value '3350'
[2023-02-24T19:35:45.859+0000] [INFO ] xrdp_wm_log_msg: sesman connect ok
[2023-02-24T19:35:45.875+0000] [INFO ] xrdp_wm_log_msg: Performing login request for peter
[2023-02-24T19:35:45.167+0000] [INFO ] xrdp_wm_log_msg: login was successful - creating session
[2023-02-24T19:35:45.173+0000] [INFO ] xrdp_wm_log_msg: session is available on display 10 for user peter
[2023-02-24T19:35:45.174+0000] [INFO ] xrdp_wm_log_msg: Connecting to session
[2023-02-24T19:35:45.176+0000] [INFO ] loaded module 'libxup.so' ok, interface size 10408, version 4
[2023-02-24T19:35:45.177+0000] [INFO ] lib_mod_connect: connecting via UNIX socket
[2023-02-24T19:35:47.178+0000] [INFO ] lib_mod_log_peer: xrdp_pid=1684 connected to Xorg_pid=1687 Xorg_uid=1001 Xorg_gid=1001 client=[::ffff:10.9.0.3]:8947
[2023-02-24T19:35:47.182+0000] [INFO ] xrdp_wm_log_msg: Connecting to chansrv
[2023-02-24T19:35:47.184+0000] [INFO ] Received memory_allocation_completecommand. width: 1656, height: 952
[2023-02-24T19:35:47.186+0000] [INFO ] server_reset:
[2023-02-24T19:35:47.988+0000] [WARN ] sanitise_extended_monitor_attributes: physical_width is not within valid range. Setting physical_width to 0mm, Setting physical_height to 0mm, physical_width was: 0
[2023-02-24T19:35:47.992+0000] [WARN ] sanitise_extended_monitor_attributes: physical_height is not within valid range. Setting physical_width to 0mm, Setting physical_height to 0mm, physical_height was: 0
[2023-02-24T19:35:47.993+0000] [WARN ] sanitise_extended_monitor_attributes: desktop_scale_factor is not within valid range of [100, 500]. Assuming 100. Value was: 0
[2023-02-24T19:35:47.994+0000] [WARN ] sanitise_extended_monitor_attributes: device_scale_factor a valid value (One of 100, 140, 180). Assuming 100. Value was: 0
[2023-02-24T19:35:48.256+0000] [INFO ] Received memory_allocation_completecommand. width: 1658, height: 953
[2023-02-24T19:35:48.398+0000] [INFO ] server_reset:
[2023-02-24T19:35:48.540+0000] [INFO ] server_reset: Advancing server monitor resized.
[2023-02-24T19:35:48.115+0000] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[2023-02-24T19:35:48.116+0000] [INFO ] xrdp_process_offscreen_bmpcache: support level 1 cache size 7864320 MB cache entries 2000
[2023-02-24T19:35:48.118+0000] [WARN ] Client Capability: not enough orders supported by client, client wants off screen bitmap but offscreen bitmaps disabled

[akarl10]

could you check what you have set in colour depth in remmina?

it should be "automatic (32bpp)". It won't work with 24bit or lower. Probably True Color 32bit without rfx or gfx will also not work

[howudodat]

oops, I had it set to 32bpp, but not automatic. works just fine now. Other than just using it are there specifics that need tested?

[howudodat]

Here's a fun one, I migrated our production xRDP server to use egfx, with the following commands:

  804  apt-add-repository ppa:saxl/xrdp-egfx
  805  apt purge xrdp xorgxrdp
  806  apt install xrdp-egfx xorgxrdp-egfx
  807  apt install pulseaudio-module-xrdp

We have both plasma and gnome installed (plasma is the default). after switching to egfx, the session was switched to gnome, even though .xsession and .xsessionrc are:

SDCP\peter@xrdp:~$ cat .xsession
startplasma-x11
SDCP\peter@xrdp:~$ cat .xsessionrc
export XDG_SESSION_DESKTOP=KDE
export XDG_DATA_DIRS=/usr/share/plasma:/usr/local/share:/usr/share:/var/lib/snapd/desktop
export XDG_CONFIG_DIRS=/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings

[akarl10]

this is expected: if you read "tweaks" above, there is written how the desktop is selected. The way you did it is not the way it should be done with this version.

short:
currently the system default is set in /etc/xdg/sesman.ini -> [SessionVariables] ->DESKTOP_SESSION
KDE would be plasma, ubuntu gnome simply ubuntu

if a user wants to set its own he should put (example with plasma)

[ -n "$XRDP_SESSION" ] && export DESKTOP_SESSION=plasma

in ~/.profile

[howudodat]

sigh...sorry for jumping over the doc

[paravz]

How does this relate to dri3/glamor hardware acceleration in xrdp (that is working stable for me) ? #1029

[adrianimboden]

Wow this is really impressive. Thanks for your work all.
I have it installed on Linux Mint and built freerdp-x11 with ffmpeg. This integration is like day and night in remote desktop usage.

I'm happy to test out any changes that you want on my system to improve the stability.

Should multi-monitor work already, or is this something that is known not to work yet?
It shows nothing and after this connection attempt, the connection has weird display issues. I have to restart the xrdp server to make it work again.

client:

$ xfreerdp /v:testserver /multimon
[23:30:56:485] [46221:46222] [INFO][com.freerdp.client.x11] - No user name set. - Using login name: adrian
[23:30:57:907] [46221:46222] [INFO][com.freerdp.gdi] - Local framebuffer format  PIXEL_FORMAT_BGRX32
[23:30:57:907] [46221:46222] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32
[23:30:57:992] [46221:46222] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd
[23:30:57:992] [46221:46222] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx
[23:30:57:126] [46221:46222] [WARN][com.freerdp.client.x11] - xf_lock_x11_:	[1] recursive lock from xf_sw_end_paint
[23:30:57:299] [46221:46222] [WARN][com.freerdp.client.x11] - xf_lock_x11_:	[1] recursive lock from xf_sw_end_paint
[23:30:57:309] [46221:46222] [WARN][com.freerdp.client.x11] - xf_lock_x11_:	[1] recursive lock from xf_sw_end_paint
[23:30:59:301] [46221:46223] [ERROR][com.freerdp.channels.rdpsnd.client] - [static] unknown msgType 39
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:00:042] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:00:042] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:00:224] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:00:224] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:02:791] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:02:791] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:02:982] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:02:982] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:02:174] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:02:174] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:03:767] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:03:767] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:03:948] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:03:948] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:05:339] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:05:339] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:05:538] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:05:538] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:05:731] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:05:731] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.
[h264 @ 0x7f2b3c018e40] No start code is found.
[h264 @ 0x7f2b3c018e40] Error splitting the input into NAL units.
[23:31:05:916] [46221:46356] [ERROR][com.freerdp.codec] - Failed to decode video frame (status=-1094995529)
[23:31:05:916] [46221:46356] [WARN][com.freerdp.gdi] - avc420_decompress failure: -1, ignoring update.

xrdp.log:

[2024-01-15T23:30:46.523+0100] [ERROR] xrdp_iso_send: trans_write_copy_s failed
[2024-01-15T23:30:46.524+0100] [ERROR] Sending [ITU T.125] DisconnectProviderUltimatum failed
[2024-01-15T23:30:46.525+0100] [INFO ] proc_enc_msg: xrdp_mm term
[2024-01-15T23:30:47.525+0100] [ERROR] Attempting to send data to a channel that is not open. channel id 1, channel status unknown
[2024-01-15T23:30:56.491+0100] [INFO ] Socket 12: connection accepted from [::ffff:10.10.100.100]:46676
[2024-01-15T23:30:56.493+0100] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[2024-01-15T23:30:56.494+0100] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[2024-01-15T23:30:56.494+0100] [ERROR] Cannot read private key file /etc/xrdp/key.pem: Permission denied
[2024-01-15T23:30:56.495+0100] [WARN ] Cannot accept TLS connections because certificate or private key file is not readable. certificate file: [/etc/xrdp/cert.pem], private key file: [/etc/xrdp/key.pem]
[2024-01-15T23:30:56.495+0100] [INFO ] Security protocol: configured [RDP], requested [SSL|HYBRID|RDP], selected [RDP]
[2024-01-15T23:30:56.496+0100] [INFO ] Connected client computer name: testclient
[2024-01-15T23:30:56.496+0100] [WARN ] Physical desktop dimensions (0x0) are invalid
[2024-01-15T23:30:56.497+0100] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc006 is unknown (ignored)
[2024-01-15T23:30:56.497+0100] [WARN ] Received [MS-RDPBCGR] TS_UD_HEADER type 0xc00a is unknown (ignored)
[2024-01-15T23:30:56.597+0100] [INFO ] xrdp_load_keyboard_layout: Keyboard information sent by the RDP client, keyboard_type:[0x04], keyboard_subtype:[0x00], keylayout:[0x00020409]
[2024-01-15T23:30:56.598+0100] [INFO ] xrdp_load_keyboard_layout: model [] variant [] layout [us] options []
[2024-01-15T23:30:56.598+0100] [INFO ] Non-TLS connection established from [::ffff:10.10.100.100]:46676 with security level : high
[2024-01-15T23:30:57.498+0100] [INFO ] xrdp_caps_process_pointer: client supports new(color) cursor
[2024-01-15T23:30:57.499+0100] [INFO ] xrdp_caps_process_codecs: RemoteFX(76772F12-BD72-4463-AFB3-B73C9C6F7886), codec id [3], properties len [49]
[2024-01-15T23:30:57.500+0100] [INFO ] Client Capability: LARGE_POINTER_FLAG_96x96 supported
[2024-01-15T23:30:57.506+0100] [WARN ] Cannot find keymap file /etc/xrdp/km-00020409.ini
[2024-01-15T23:30:57.506+0100] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini
[2024-01-15T23:30:57.508+0100] [WARN ] local keymap file for 0x00020409 found and doesn't match built in keymap, using local keymap file
[2024-01-15T23:30:57.509+0100] [WARN ] No information is available to determine login screen DPI
[2024-01-15T23:30:57.510+0100] [WARN ] No DPI value is available to find login font
[2024-01-15T23:30:57.510+0100] [WARN ] Using the default_dpi of 96
[2024-01-15T23:30:57.684+0100] [INFO ] xrdp_egfx_create: error 0 channel_id 1
[2024-01-15T23:30:57.705+0100] [INFO ] xrdp_mm_egfx_caps_advertise:
[2024-01-15T23:30:57.705+0100] [INFO ]   version 0x00080004 flags 0x00000001 (index: 0)
[2024-01-15T23:30:57.706+0100] [INFO ]   version 0x00080105 flags 0x00000013 (index: 1)
[2024-01-15T23:30:57.706+0100] [INFO ]   version 0x000a0002 flags 0x00000002 (index: 2)
[2024-01-15T23:30:57.707+0100] [INFO ]   version 0x000a0200 flags 0x00000002 (index: 3)
[2024-01-15T23:30:57.707+0100] [INFO ]   version 0x000a0301 flags 0x00000040 (index: 4)
[2024-01-15T23:30:57.708+0100] [INFO ]   version 0x000a0400 flags 0x00000042 (index: 5)
[2024-01-15T23:30:57.708+0100] [INFO ]   version 0x000a0502 flags 0x00000042 (index: 6)
[2024-01-15T23:30:57.709+0100] [INFO ]   version 0x000a0600 flags 0x00000042 (index: 7)
[2024-01-15T23:30:57.709+0100] [INFO ]   replying version 0x000a0600 flags 0x00000042
[2024-01-15T23:30:57.710+0100] [INFO ] xrdp_mm_egfx_caps_advertise: xrdp_egfx_send_capsconfirm error 0 best_index 7
[2024-01-15T23:30:57.710+0100] [INFO ] xrdp_egfx_reset_graphics:
[2024-01-15T23:30:57.710+0100] [INFO ] xrdp_egfx_reset_graphics: (index 0) monitor left 2560 top 0 right 6399 bottom 1599 is_primary 1
[2024-01-15T23:30:57.711+0100] [INFO ] xrdp_egfx_reset_graphics: (index 1) monitor left 0 top 160 right 2559 bottom 1599 is_primary 0
[2024-01-15T23:30:57.711+0100] [INFO ] xrdp_egfx_reset_graphics: width 6400 height 1600 monitorcount 2
[2024-01-15T23:30:57.712+0100] [INFO ] xrdp_mm_egfx_caps_advertise: xrdp_egfx_send_reset_graphics error 0 monitorCount 2
[2024-01-15T23:30:57.712+0100] [INFO ] xrdp_encoder_create:
[2024-01-15T23:30:57.712+0100] [INFO ] xrdp_encoder_create: starting h264 codec session gfx
[2024-01-15T23:30:57.713+0100] [INFO ] xrdp_mm_egfx_invalidate_all:
[2024-01-15T23:30:57.713+0100] [INFO ] xrdp_mm_egfx_caps_advertise: egfx created.
[2024-01-15T23:30:57.799+0100] [ERROR] dynamic_monitor_open_response: error
[2024-01-15T23:30:57.800+0100] [ERROR] xrdp_rdp_recv: xrdp_channel_process failed
[2024-01-15T23:30:59.945+0100] [WARN ] Ignoring obsolete SCP port value '3350'
[2024-01-15T23:30:59.946+0100] [INFO ] xrdp_wm_log_msg: sesman connect ok
[2024-01-15T23:30:59.947+0100] [INFO ] xrdp_wm_log_msg: Performing login request for adrian
[2024-01-15T23:30:59.984+0100] [INFO ] xrdp_wm_log_msg: login was successful - creating session
[2024-01-15T23:30:59.985+0100] [INFO ] xrdp_wm_log_msg: session is available on display 10 for user adrian
[2024-01-15T23:30:59.986+0100] [INFO ] xrdp_wm_log_msg: Connecting to session
[2024-01-15T23:30:59.986+0100] [INFO ] loaded module 'libxup.so' ok, interface size 10416, version 4
[2024-01-15T23:30:59.987+0100] [INFO ] lib_mod_connect: connecting via UNIX socket
[2024-01-15T23:30:59.987+0100] [INFO ] lib_mod_log_peer: xrdp_pid=3007 connected to Xorg_pid=1238 Xorg_uid=1000 Xorg_gid=1000 client=[::ffff:10.10.100.100]:46676
[2024-01-15T23:30:59.988+0100] [INFO ] xrdp_wm_log_msg: Connecting to chansrv
[2024-01-15T23:31:00.470+0100] [INFO ] Received xorgxrdp_helper_x11_create_pixmap command. width: 3840, height: 1600, magic: -559038737, con_id 2, mon_id 0
[2024-01-15T23:31:00.470+0100] [INFO ] server_reset:
[2024-01-15T23:31:00.471+0100] [INFO ] Received xorgxrdp_helper_x11_create_pixmap command. width: 2560, height: 1440, magic: -559038737, con_id 2, mon_id 1
[2024-01-15T23:31:00.471+0100] [INFO ] server_reset:

[Nexarian]

Multimonitor is still a work in progress for EGFX!

[zd9999cs]

This really speed xrdp connection up. Only issue I encounter is when I was remote connecting to my ubuntu computer using microsoft remote desktop in fullscreen mode. When the remote desktop software window lose focus and regain focus, the remote desktop freezes and I have to reconnect to regain control.

[thenik]

Hi,

Clean install , does not work at debian =)
I tried via
apt-add-repository ppa:saxl/xrdp-egfx
because there is no apt-add-repository command.
I tried the next
sudo apt-get install software-properties-common

but still cannot install via apt-add-repository ppa:saxl/xrdp-egfx

any ideas how to install that ?

[zorba128]

snap does not work fully in XRDP_USE_MULTISESSION mode (mainly sound and maybe open file dialog issues). flatpak works tough

I believe DBUS is not working for snap apps with XRDP_USE_MULTISESSION. In my case this resulted in firefox (from snap) unable to open links ("Firefox is already running, but is not responding" popup). So for now I had to disable this feature.

[akarl10]

dbus should work, but firefox is not multisession compatible (it can only be launched one time per user per machine/profile folder). The multisession issue with snaps is actually pulseaudio/sound

again, XRDP_USE_MULTISESSION is not really meant for snap. Personally I always apt purge snapd and use firefox from a ppa. I understand though that this is not feasible for ubuntu desktop. For plasma it works quite well though

[zorba128]

I'm not using multiple sessions. I just wanted to have this flag enabled to avoid black-screen when I forget to logout locally
before opening remote connection (this was the behavior with original xrdp, to be honest I did not test it with egfx one).

Problem described above happens for with just me logged in once over rdp.
And disabling XRDP_USE_MULTISESSION fixed it.

[philstopford]

I'm a little puzzled at the moment. I'm running Endeavour OS (Arch-derived) and it's not entirely clear to me which features and settings are upstreamed. I'd love to have the nvidia acceleration and multi-session capabilities active; what's the correct way to proceed? 'Vanilla' xrdp is running fine, but is slow on the systems at the moment, with remmina as the client. Is there a summary / wiki overview of status, etc. somewhere to make it easy to get up to speed on the efforts?

[bo-qeye]

I am very intrigued. Would an aging Nvidia Quadro P2000 be able to accelerate this?

[Nexarian]

The Quadro P2000 should be fine. Maybe a bit slow, but it'll work. As long as the Nvidia drivers advertise NVENC support on the hardware.

[sonnguyenjb]

Hello @akarl10 , first of all, thank you and the team so much for adding such significant improvements to xrdp with egfx features. I noticed that there have been some improvements and fixes related to efgx added to the project since the last build on the PPA. Could you update the ubuntu PPA with the latest code? I desperately want to try it out, but I don't know how to build the .deb package for Ubuntu, I did try some guides but I'm not able to make it work. Many thanks.

[akarl10]

egfx got merged already with the exception of h264.
For that I don't know a working branch that is currently stable enough (mainline_merge_shm crashes Xorg when connecting with h264)
Also note that this ppa has a "hybrid" lrandr/glamour patch so that there is no need for different nvidia/non nvidia packages. I don't have such a hybrid for the encoder helper so this might be the source of the issue I'm facing. In the long term maybe such a split might be necessary, although nvidia should really fix there X11 driver so that it works like the others (that is egl/glamor) since at the end of the day the lrandr thing is a hack.

I might update my ppa if @Nexarian can tell me what the best testdrive branch would be

[Nexarian]

So there have been multiple titanic shifts in the underlying code of the devel branch of XRDP. The first was a security-motivated change to shm, which was the origin of mainline_merge_shm. SHM changed how the memory buffer between xrdp and xorgxrdp worked, which broke all the things.

Then we did a major push to integrate the basic framework of GFX into devel, which is nearly done, but the amount of changes from the original mainline_merge were significant enough that a rebase would be extremely time consuming

So instead my plan is to rebuild mainline_merge off of devel from whole cloth. There's still a lot that mainline_merge offers that isn't in devel, mainly H264 and hardware-accelerated H264, and this is where Nvidia comes in. devel still won't work with hardware accelerated NVIDIA.

I should be able to start work on that with a target finish by end of March 🤞

[philstopford]

How goes the progress for nVidia?

[alexhostrup]

Is it possible to build this on Alpine?

[metalefty]

Try it and share the result!

[bo-qeye]

I wanted to try this on an Google Cloud instance, as that would mean easy access to a variety of GPUs.

Is this a dumb idea? Will the gains from the GPU be nullified by the latency to the cloud? (I'm sitting approximately 20ms away.)

What would be a good GPU for this? The list of available ones is here

Edit: I got this to work. Ubuntu 23, don't forget to install GNOME, went with a n1-standard-4 with a single NVIDIA T4 GPU core. Can't really tell if it's snappy or not. Input greatly appreciated.

[adrianog]

are you running it in a container?

[johntdavis84]

@akarl10 , hello!

I've got some confusing issues when connecting to a Lubuntu 22.04 VM, and I'm not sure if it's just that I'm using an older version of the xrdp-egfx package because I'm not on 24.04 yet (Soon®), or if I've got something misconfigured.

My RDP client is the "Windows app" on a Mac, which is just a renamed Microsoft RDP client.

Inside the VM, the UFO test tells me I'm running at 60 FPS (well, 59 FPS). That's the result I'd expect.

However, I can't change resolutions away from 1152x2048, and xrandr is either very confused or reporting an actual issue.

Inside the VM:

1. Where is it getting that Screen0 size of 4096x1152 Is that a virtual screen that it cannot exceed?
2. rdp0 and rdp1 are the dual virtual displays that come up when I connect. They're reporting as 2048x1152, which I don't love and would like to change, but I can't figure out how. My client displays are LG Ultrafine 4K displays, so I think I could correctly render higher-res, even though the way Apple does display scaling is confusing to me.
3. Is it telling me my client-side refresh rate is 25 Hz?

The Mac "Windows app" doesn't have any options to force a refresh rate, and I can't figure out if it's even possible to set a desired resolution on the client.

Is there a way I can force 60 Hz and or 4K resolution server side?

[akarl10]

I don't think it is possible to force the resolution server side, usually that information comes from the client.

The 22.04 version runs at 25fps (like the encoder has that more or less hardcoded). The version in 24.04 is based on mainline so it is possible to fiddle with the encoder timings. It seems to still report 50hz instead of 60, but h264 is set to 16ms, that should be ~60hz

what resolution would you expect, as far as i can see xrdp things there are two monitors, the "primary" is on the right and both have a resolution of 2048x1152.

What I don't know is (because of lack of hardware) if there is (or was) a limit in xrdp of 4096 pixels per dimension
#3083 would hint there may be issues..

[johntdavis84]

Thanks for your reply. :)

I don't think it is possible to force the resolution server side, usually that information comes from the client.

Oh, good. That actually makes things simpler. I was afraid I hadn't configured Lubuntu or xrdp correctly somehow. It's also really hard to teach yourself how to actually tune xrdp. It's pretty impenetrable, and there's about eleventy billion options and a lot of outdated stuff surfaced high in Google searches. :P

The 22.04 version runs at 25fps (like the encoder has that more or less hardcoded).

Ah. Cool. I don't mind it being 25 fps, but I thought it was that way because I hadn't done something I was supposed to do.

(Separately, my windows VM is capped at 30 fps even though I did the registry thing to enable 60 fps, but that's a whole other thing that's surely Microsoft's fault somehow.)

You've given me another reason to test the 24.04 version of my SDR linux distro now. It'll be interesting to see if I can easily get 60 fps out of it. I think it'll work; the UFO test website already thinks the VM OS is running at 60 fps. RDP is slowing it down.

what resolution would you expect, as far as i can see xrdp things there are two monitors, the "primary" is on the right and both have a resolution of 2048x1152.

This is the behavior I'm seeing, and is now that I know the frame rate is correct I can test different resolution settings.

2048x1152 is fine, and performs well, but the UI is scaled to be large in the entire VM, and the app I'm using is pretty crowded. I was wanting to try something like 1440p. I'd rather not get into a fight with Linux about UI scaling if I can avoid it.

After sending my previous message, I did find this page from Microsoft re: setting the resolution client-side: https://learn.microsoft.com/en-us/windows-app/display-settings?tabs=macos

Regarding setting the resolution, it says:

This setting is only available when Use all monitors, Optimize for Retina displays and Update the session resolution on resize are unchecked.

So, since I've been using two displays, I haven't had the option for resolution switching.
So far, I've discovered that enabling Retina mode with two monitors give me two 4K displays, with Linux's blindness-inducing underscaled UI.

glxgears has trouble pinning to 59 fps in 4K mode, and wavers back and forth about 2-4 fps, so that's probably asking a bit much.

If I disable one of the displays so I have a single virtual monitor, I can manually request 1440p or 1800p (2880x1800). I'll experiment with those, as well. I don't need 4K, per se, but having the extra room at least from 1440p would be nice.

[OSMaxwell]

Wonderful work. This is my number one package to install after a fresh Ubuntu installation (Even on 24.04)!

One thing I noticed since ~2023:

There is a quality/sharpness loss, even when connected at 3440 x 1440. (Intel UHD Graphics 630)

I have all caching and compression settings in xrdp.ini set to off and it still happens. It goes away when I move back to default xrdp from ubuntu (0.9.24), but that solution is obviously slow.

[akarl10]

The 24.04 package uses xrdp/devel as basis, not Nexarian's. I've done this since the nvidia patches did not work reliably on my (only) nvidia system. The package also was a kind of a hybrid since it could run both nvidia and egl (=/dev/renderD128). This was hard to debug and maintain so I switched back to xrdp/devel when egfx was merged.

debian' freerdp package has h264 enabled, I know that. I was talking about ubuntu.
and about avc444/ 4:4:4:
#3375
I would say that this means this is not merged yet

[tabletseeker]

This was hard to debug and maintain so I switched back to xrdp/devel when egfx was merged.

Wait, they merged it already?
I had no idea. Was this from a pull request or just spontaneously, because I thought they always rejected it due to 'reliability issues'. Nexarian's mainline is old af, but I thought there was no alternative so I put up with it.

debian' freerdp package has h264 enabled, I know that. I was talking about ubuntu. and about avc444/ 4:4:4: #3375 I would say that this means this is not merged yet

Ok yeah, not sure about Ubuntu.

I made a repo to automate the whole process + sriov dkms installation. If xrdp/devel really merged egfx then obviously I'm gonna switch to that then.
https://github.com/tabletseeker/xrdp_vaapi

[akarl10]

@OSMaxwell When I connect via freerdp and /gfx:rfx I don't get that issue. Of course performance is not as good as it would be with h264, but still way better than with the stock xrdp version without gfx at all (thus using gdi)

[OSMaxwell]

@akarl10 I connect via Windows Remote Desktop (Windows 11), with xrdp-egfx-0.10.80-20241223

[akarl10]

@OSMaxwell you may try to disable h264 server side and only enable rfx progressive:
edit the file /etc/xrdp/gfx.toml, specifically change order = [ "H264", "RFX" ] to order = [ "RFX" ], restart xrdp or the machine and see what happens

[tabletseeker]

Is this the pull request that merged egfx? Just says base functions
#2338 (comment)

[johntdavis84]

Re: 4:4:4 and h264 support:

It's my understanding that when we're using the Microsoft Remote Desktop app on a Mac (excuse me, "Windows.app," now), we're using h264, at 4:2:0?

I think there's a registry tweak in Windows 11 to enable 4:4:4 over RDP, but I haven't tried it yet. I'm still stuck at 30 FPS in that Windows VM, even though I did the registry tweak that's supposed to enable 60 FPS over RDP.

The default settings in my Lubuntu VM deliver 60 FPS to my client without a problem, even though the monitor I'm using on the client can't do more than 30 FPS (to my great annoyance; it's a 60 FPS monitor but just got old apparently).

I'm not sure what the equivalent would be to specify/verify 4:4:4/best codec when connecting to an Ubuntu VM. Something in sesman.ini?

[Nexarian]

4:4:4 NVENC doesn't yet work stably on XRDP. I had an old branch where I tried it: https://github.com/Nexarian/xrdp/tree/mainline_merge_avc444

The output on the Mac OS client was garbled, and I never figured out why.

[johntdavis84]

Thanks for your reply. :)

I'm actually using a 12th gen i7-12700T, with the UHD 770 (UHD 750 with higher clocks).
See 11th and 12th-gen encoder information, here: https://www.intel.com/content/www/us/en/docs/onevpl/developer-reference-media-intel-hardware/1-1/details.html#ENCODE-11-12

I'm not entirely sure that I'm reading it right, but looking at 4:4:4 encoding, I think it supports:

• AVC/H264, MPEG2: 8-bit, 4:2:0 (NV12)
• MJPEG: 4:4:4 (AYUV)
• HEVC/H265: 8-bit, 4:4:4 (AYUV), 10-bit, 4:4:4 (Y410)
• HEVC (Hardware Function, Shader-Based): 4:2:2 and 4:2:0 only
• VP9: 8-bit, 4:4:4 (AYUV), 10-bit, 4:4:4 (Y410)

Is NV12 the NVENC encoder? For some reason, I was assuming that NVIDIA encoders weren't present on Intel cards. I just learned something ... kind of confusing. I guess they license them?

VP9 support is irrelevant at least until the patents expire.

I know Microsoft's implementation of RDP supports H.265, but I'm not sure what the situation is with xrdp.

Doubly annoying: The Mac RDP client (now Windows.app) doesn't actually seem to have an option to tell you what encoding your connection is using. The Connection Information it does give you is next to useless for troubleshooting graphics quality issues. I need to test it from a Windows RDP client and see if it's any better.

...Or just find an actually decent Mac RDP client.

[Nexarian]

NVENC supports 4:4:4. That's not the issue. The issue is that Microsoft has a bug in their "Windows App" (I hate that name) on Mac OS that basically doesn't work with this branch.

Nvidia encoders are not present on Intel cards. Intel has their own implementation of an H264 encoder. On processors with an iGPU it's called QuickSync, I'm unsure what the situation is with their new desktop card line, but I know it also supports the encoder. The problem with Intel's system is the APIs are VERY difficult to work with (an order of magnitude harder than NVENC/CUDA), and the YAMI API that we relied on is now deprecated. Jay and I have been thinking about what to do here.

I thought that the H265 rollout for RDP was up-and-coming but wasn't here yet. @jsorg71 ?

NV12 is a specific sub-encoding of the YUV 4:2:0 color space: https://paulbourke.net/dataformats/nv12/

FreeRDP and MSTSC seemed fine with my 4:4:4 implementation, however. But Mac OS is important enough that it blocked the rollout of this feature. I haven't been able to discuss this with Microsoft yet for a large number of reasons.

You are correct that very few clients other than FreeRDP have toggle options that allow you to directly specify the encoding. That used to be possible with things like MSRDC, but they DRM'ed the RDP file so now we can't use that. It's probably considered an "advanced" feature that most users don't care about. It took awhile for me to even confirm that my Windows 11 -> Windows 11 connection was actually using 4:4:4.

[johntdavis84]

Thanks for the info. That clears things up a lot. As someone who doesn't work with these standards, a lot of the terms are confusing right now. Hopefully, I'll be able to understand more going forward. :)

I didn't know part of the Intel API had been depreciated. That doesn't sound good. Is that part of the the non-free Intel VA-API media encoding driver? https://github.com/intel/media-driver

I thought that the H265 rollout for RDP was up-and-coming but wasn't here yet. @jsorg71 ?

Hopefully, it's not lost in whatever vortex the 12th and 13th gen SR-IOV features are stuck in. Those have been coming any minute now since kernel 6.9.

You are correct that very few clients other than FreeRDP have toggle options that allow you to directly specify the encoding.

That would be awesome, but at this point I'd just like to see what encoding/FPS/etc. a connection is using. The Windows.app ( sigh ) is completely useless there. And it's started glitching out. It won't stay in full screen when the client's display goes to sleep, even if the client itself doesn't sleep. Awesome.

Really appreciate all the work you've done on this. I'm using it for almost all the VDI work I do in my SOHO network. I couldn't do a lot of what I'm doing now without it. It's really the simplest, most reliable way to leverage an Intel iGPU for VDI in a Proxmox server, IMO.

It took awhile for me to even confirm that my Windows 11 -> Windows 11 connection was actually using 4:4:4

How did you actually get useful diagnostic information out of Windows 11? :-P

[jsorg71]

Most of the bits from mainline merge have been merged to devel including most of the nvidia hack bits. It should be stable.
The bits that have not made it yet are

• Intel hardware encoder because libyami has been archived
• yuv 444 bits because, like Nex said, not stable yet.

xrdp PRs, there are other PRs for xorgxrdp not listed here.
#3320 nvenc hardware
#3311 openh264 software
#3073 x264 software

[tabletseeker]

* Intel hardware encoder because libyami has been archived

Yes, I was wondering about this.

Would it be possible to simply modify the xrdp/devel Makefile and other stuff to build with --enable-yami?
Like for example in Makefile.am

if XRDP_YAMI
ldlibrarypath=LD_LIBRARY_PATH=/usr/local/lib
libvadriverspath=LIBVA_DRIVERS_PATH=/usr/local/lib/dri
else
ldlibrarypath=
libvadriverspath=
endif

* yuv 444 bits because, like Nex said, not stable yet.

@Nexarian has an xrdp/avc444 branch: https://github.com/Nexarian/xrdp/tree/mainline_merge_avc444

I tested it, but didn't notice any major difference between /gfx:avc420 and /gfx:avc444 in xfreerdp.

[Nexarian]

If you have a beefy enough system you won't notice anything other than small improvements in graphical fidelity. This is partially why it hasn't been a huge priority. The only people who care are nit-picky devs who complain about "fuzzy text."

[tabletseeker]

If you have a beefy enough system you won't notice anything other than small improvements in graphical fidelity. This is partially why it hasn't been a huge priority. The only people who care are nit-picky devs who complain about "fuzzy text."

@Nexarian Right, I'm just using a mobile Alderlake system, but couldn't really notice a difference.

Just to confirm, your mainline_merge branch is still the only fork of xrdp offering h264 + intel hw acceleration with va-api?

I learned a lot from your commits and would like to contribute so that we can get this merged with the latest neutrinolabs/xrdp.

What's stopping them anyway? libyami support has stopped, but it still works nonetheless.

Like I suggested above, do we just need to modify the Makefile in order to build with --enable-yami or are deeper changes needed in the code?

[jsorg71]

Matt expressed interest in putting the latest libyami in our thirdparty for our use in xrdp.
If you guys see value in that I can put together a PR.
Even if we do use libyami now, I would still like to work on a direct libva version later.

Just a bit of explanation of what libyami is. libyami is a helper library to make using libva easier. Intel and many other hardware companies out there are NOT giving up on libva. libva is very much still in active development. Intel just doesn't want to support libyami anymore. It's not just libyami, they archived MediaSDK too.

https://github.com/intel/libyami
https://github.com/Intel-Media-SDK/MediaSDK

[tabletseeker]

Matt expressed interest in putting the latest libyami in our thirdparty for our use in xrdp. If you guys see value in that I can put together a PR. Even if we do use libyami now, I would still like to work on a direct libva version later.

Broadly speaking, what would this pull request look like?

[matt335672]

I'm happy to look at that if we can get something working sooner. The risk of course is that we don't manage to get the port to libva sorted before libyami becomes unbuildable on modern systems.

[l-acad-pro]

I'm getting this error. I'm using it wish WSL. I have Ubuntu 24.04 and GNOME installed.

[akarl10]

There are some things that you can check:

• I suppose you used xrdp-egfx from the ppa mentioned above: did you also install xorgxrdp-egfx?
• check the existence of /usr/lib/xorg/Xorg. If it is not installed, do apt install xserver-xorg-core
• check the logfile /var/log/xrdp-sesman.log (maybe post the last few lines here)

[l-acad-pro]

I installed Nexarian script and tried again. It didn't work. That's what I get from the log file:

[2025-08-18T15:31:54.427-0300] [INFO ] Received request from xrdp to create a session for user teste
[2025-08-18T15:31:56.163-0300] [INFO ] Starting X server on display 10: Xorg :10 -auth .Xauthority -config xrdp/xorg_nvidia.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
[2025-08-18T15:32:06.158-0300] [ERROR] waitforx: Unable to open display :10
[2025-08-18T15:32:06.267-0300] [ERROR] X server failed to start
[2025-08-18T15:32:06.356-0300] [INFO ] Session on display 10 has finished.

[akarl10]

you said that you run under wsl: I dont think there is a way X works with the real nvidia drivers (you are effectivly running xrdp in a vm, not on your hardware. The linux subsystem has no direct pci access to the hardware).
This should not be an issue since in wsl there is a virutal gpu "accessibe" as /dev/dxgi and mesa has all drivers needed, so it should pick up that driver automatically (maybe, I don't run a windows system).
If you force it to use the config xrdp/xorg_nvidia.conf X probably crashes immediatly and that is probably why you get this error ( you can counter check the file $HOME/.xorgxrdp.10.log, but it probably says it cannot load/initialize nvidia due to not finding a gpu)

[l-acad-pro]

Sorry, I thought my linux subsystem had access to my GPU directly.
I did a little research and I learned more about mesa. Is it possible to force WSL in using mesa or any kind of graphics acceleration instead of using only the CPU in RDP connections?

[akarl10]

I don't have a windows 11 machine, let alone one with a nvidia gpu, so I cannot help you there.
Things like cuda and nvenc should already work. For video decoding setting the environment variable
LIBVA_DRIVER_NAME=d3d12 in sesman.ini section [SessionVariables] may enable that.
as for 3d: Don't know if that's currently possible.
What's probably needed is (if its even there) whitelisting the drm driver:
what does cat .xorgxrdp.10.log | grep rdpPre output? There should be a line name [XXXXX]. the XXXX would be the string that needs to be added to the DRMAllowList in /etc/X11/xrdp/xorg.conf
additionally (try this later) GALLIUM_DRIVER=d3d12 might be needed too in [SessionVariables]

other then that: You need someone with a windows 11 machine that can help you..

[Velorx]

Hello, I'm sorry from the start if I'm asking something obvious here, but I've been baffled by all the information everywhere.

Does EGFX pipeline actually work with NVidia GPUs for hardware acceleration like the original pipeline in xrdp works? I've managed to get NVidia GPU acceleration working on the xrdp package, but I've struggled with the egfx package...

If the answer is yes, some small pointer to how to get it working would be awesome.

[Velorx]

@akarl10

I actually checked the sesman log before and Idk how that hell I missed that, but here it is:

[2025-08-19T19:53:23.605+0100] [INFO ] Received system login request from xrdp for user: server-admin IP: ::ffff:192.168.0.16
[2025-08-19T19:53:23.606+0100] [ERROR] Connection is already logged in for server-admin
[2025-08-19T19:53:23.609+0100] [ERROR] sesexec_main_loop: trans_check_wait_objs failed for ECP transport
[2025-08-19T19:53:34.204+0100] [INFO ] Socket 13: connection accepted from AF_UNIX
[2025-08-19T19:53:34.208+0100] [INFO ] Received system login request from xrdp for user: server-admin IP: ::ffff:192.168.0.16
[2025-08-19T19:53:34.215+0100] [INFO ] starting xrdp-sesexec with pid 2940
[2025-08-19T19:53:34.222+0100] [INFO ] TerminalServerUsers group tsusers doesn't exist. Access granted for server-admin
[2025-08-19T19:53:34.224+0100] [INFO ] Access permitted for user: server-admin
[2025-08-19T19:53:34.225+0100] [INFO ] Received sys login status for server-admin : logged in
[2025-08-19T19:53:34.228+0100] [INFO ] Received request from xrdp to create a session for user server-admin
[2025-08-19T19:53:34.230+0100] [INFO ] Passing session creation request to sesexec
[2025-08-19T19:53:34.250+0100] [INFO ] Starting X server on display 10: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg_nvidia.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log 
[2025-08-19T19:53:44.271+0100] [ERROR] scp_list_check_wait_objs: trans_check_wait_objs(1) failed, removing trans
[2025-08-19T19:53:45.257+0100] [ERROR] waitforx: Unable to find any RandR outputs
[2025-08-19T19:53:45.259+0100] [ERROR] An error occurred waiting for the X server

[akarl10]

@verlox will try to release a new package tomorrow. actually there is something missing (there should be rdpLRRInit: AddCallback ok somewhere..
I myself test on a debian build of the plucky version of the package that will land in the ppa. the lts version get only updates if I am absolutely sure I don't break anyone's current setup (I consider the nvidia reenabling experimental because I don't have any feedback, well now yours which I appreciate, the hint with "Unable to find any RandR outputs" actually pointed me to the packaging problem).

[Velorx]

@akarl10

Yeah no worries, I should actually thank you. Both for making this package and taking your time to troubleshoot this with me - No rush.

[akarl10]

Depending how fast launchpad is the update should land in about an hour. Please make sure when updating this time to let the update replace your config files and reenable XRDP_USE_ACCEL_ASSIST=1 afterwards. The automatic update will probably do something unexpected with the param= lines..

[Velorx]

@akarl10

I've downloaded the newest package you've published and I can confirm that everything does indeed work pretty much out of the box. Note that I still had to uncomment:

Section "Files"
    ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg,/usr/lib/xorg/modules"
EndSection

Other that that all is great! OpenGL uses the GPU and everything seems so smooth!

Thank you very much, if you need any further help with testing, I'm down to test things out.

[rikardthomasson]

This fork reduces cpu load greatly when running on the CPU. However, when enabling HW acceleration (XRDP_USE_ACCEL_ASSIST=1) my windows client (mstsc) shuts down complaining about a protocol error from the server. Couldn't find any good clue in the server logs. I am using a Sapphire Radeon RX 570 Nitro+ 8GB GPU and LXDE desktop.

Is this a known issue?

[akarl10]

actually yes.
XRDP_USE_ACCEL_ASSIST enables hardware 264 encoding (not to be confused with hardware 3d rendering). This however works only with a nvidia gpu (nvenc). There is currently no safeguard against this invalid configuration and the connection simply drops. the amd/intel counterpart that would probably go through libva is not implemented.

[rikardthomasson]

Thanks for the reply. It is HW h264 encoding I am after, and I had not understood that this fork only supports nvidia. Again, thanks for the clarification.

[johntdavis84]

actually yes. XRDP_USE_ACCEL_ASSIST enables hardware 264 encoding (not to be confused with hardware 3d rendering). This however works only with a nvidia gpu (nvenc). There is currently no safeguard against this invalid configuration and the connection simply drops. the amd/intel counterpart that would probably go through libva is not implemented.

Was fooling around and enabled the h264 hardwware encoding on an Intel iGPU and ran into the same thing. Thanks for clarifying that.

Is this something that y'all could fix eventually, or does it have to be addressed upstream?

[johntdavis84]

I just set up an Ubuntu 24.04 LTS VM with this xrdp package, and have it working with audio and GPU acceleration with an Intel i7-12700T iGPU. :)

One odd thing I've noticed, though:
xrandr is reporting a 50 Hz framerate, instead of the 60 fps I expected.
The ufo test website is reporting 58-59 fps.
Likewise, the webGL aquarium test is giving me a locked 59 fps.

Is this normal/expected behavior?

I'm inclined to believe the reports from webGL aquarium and the ufo test--it seems unlikely they'd both lie in my favor. It makes more sense that xrandr is old and confused.

johntdavis@dragon-radio:~$ uname -a && echo && lsb_release -a && echo && apt search xrdp | grep -i "installed" && glxinfo
Linux dragon-radio 6.14.0-29-generic #29~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Aug 14 16:52:50 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.3 LTS
Release:        24.04
Codename:       noble

libpipewire-0.3-modules-xrdp/noble,now 0.2-2 amd64 [installed,automatic]
pipewire-module-xrdp/noble,noble,now 0.2-2 all [installed]
xorgxrdp-egfx/noble,now 1:0.10.80-20250813-1ubuntu1+0egfx6~noble amd64 [installed]
xrdp-egfx/noble,now 0.10.80-20250813-1ubuntu1+0egfx1~noble amd64 [installed]

Is this an actual problem, or just an xrandr issue?

[vszakd]

I've read some conflicting messages. Could you please confirm that xrdp-egfx only supports NVIDIA and not Intel graphics cards? Thanks

[johntdavis84]

Was there a signficant update for Noble-based systems in late October?

Surprised to see an update in apt.

[johntdavis84]

Sure! I'm glad to be able to help with something; hacking on the code in this repo is a (quite a) bit over my head. :)

I've previously used Lubuntu in sesman.ini to get my actual Lubuntu desktop with background and icons, but it no longer seems to respect that setting. Right now it appears to be using Openbox, no matter what i set for DESKTOP_SESSION. I'm still not sure why.
EDIT: This might be normal for this distro. It looks like it's configured to use Openbox as the Window Manager, but LXQT is also running. I can see them both in htop.

I'm not yet very familiar with how the Xession files are put together, but I noticed that the Lubuntu.desktop file only has an Exec line. The LXQt file also includes a TryExec line, as does the Openbox file.

Files below, with file names.

johntdavis@dragon-radio:/usr/share/xsessions$ ll
Permissions Size User Date Modified Name
.rw-r--r--   123 root 17 Apr  2024   Lubuntu.desktop
.rw-r--r--  2.2k root  8 Apr  2024   lxqt.desktop
.rw-r--r--   198 root  8 Apr  2024   openbox.desktop
johntdavis@dragon-radio:/usr/share/xsessions$ cat openbox.desktop 
[Desktop Entry]
Name=Openbox
Comment=Log in using the Openbox window manager (without a session manager)
Exec=/usr/bin/openbox-session
TryExec=/usr/bin/openbox-session
Icon=openbox
Type=Application

johntdavis@dragon-radio:/usr/share/xsessions$ cat Lubuntu.desktop 
[Desktop Entry]
Name=Lubuntu
Comment=Lubuntu session using LXQt
Exec=/usr/bin/startlxqt
Type=Application
DesktopNames=LXQt

johntdavis@dragon-radio:/usr/share/xsessions$ cat lxqt.desktop 
[Desktop Entry]
Type=Application
Exec=startlxqt
TryExec=lxqt-session

DesktopNames=LXQt
Name=LXQt Desktop
Comment=Lightweight Qt Desktop
Name[ar]=سطح المكتب ريزر
Comment[ar]=سطح المكتب كيوت٤
Name[cs]=Plocha LXQt
Comment[cs]=Pracovní plocha na Qt
Name[da]=LXQt-skrivebord
Comment[da]=Letvægts Qt-skrivebord
Name[de]=LXQt Arbeitsumgebung
Comment[de]=Leichtgewichtige Qt Arbeitsumgebung
Name[el]=Επιφάνεια εργασίας LXQt
Comment[el]=Ελαφριά επιφάνεια εργασίας Qt
Name[eo]=LXQta labortablo
Comment[eo]=Qt-labortablo
Name[es]=Escritorio LXQt
Comment[es]=Escritorio Qt ligero
Name[es_VE]=Escritorio LXQt
Comment[es_VE]=Escritorio Qt
Name[eu]=LXQt mahaigaina
Comment[eu]=Qt mahaigaina
Name[fi]=LXQt-työpöytä
Comment[fi]=Qt-työpöytä
Name[fr]=Bureau LXQt
Comment[fr]=Bureau léger pour Qt
Name[hr]=Radna površina LXQt
Comment[hr]=Jednostavna radna površina za Qt
Name[hu]=LXQt asztal
Comment[hu]=Qt asztali környezet
Name[it]=Desktop LXQt
Comment[it]=Desktop Qt
Name[ja]=LXQt デスクトップ
Comment[ja]=Qt デスクトップ
Name[lt]=LXQt darbalaukis
Comment[lt]=Supaprastintas Qt darbalaukis
Name[nl]=LXQt Bureaublad
Comment[nl]=Qt Bureaublad
Name[pl]=Pulpit LXQt
Comment[pl]=Środowisko graficzne Qt
Name[pt]=Ambiente de trabalho LXQt
Comment[pt]=Ambiente de trabalho em Qt
Name[pt_BR]=Área de trabalho LXQt
Comment[pt_BR]=Área de trabalho Qt
Name[ro]=Desktop LXQt
Comment[ro]=Desktop Qt
Name[ru]=Рабочий стол LXQt
Comment[ru]=Рабочий стол  на Qt
Name[sk]=Prostredie LXQt
Comment[sk]=Pracovné prostredie v Qt
Name[sl]=Namizje LXQt
Comment[sl]=Namizje, ustvarjeno s Qt
Name[sr]=Рејзорова радна површ
Comment[sr]=Кјут4 радна површ
Name[sr@latin]=Rejzorova radna površ
Comment[sr@latin]=Qt radna površ
Name[th_TH]=เดสก์ท็อป LXQt
Comment[th_TH]=เดสก์ท็อป Qt
Name[tr]=LXQt Masaüstü
Comment[tr]=Qt Masaüstü
Name[uk]=Стільниця LXQt
Comment[uk]=Стільниця Qt
Name[zh_CN]=LXQt 桌面
Comment[zh_CN]=轻量级的 Qt 桌面环境
Name[zh_TW]=LXQt桌面
Comment[zh_TW]=輕量級Qt桌面環境

[johntdavis84]

i would expect a rdp session behaves the same as a local one regarding icons.. the possible values for DESKTOP_SESSION is essentially the file name in /usr/share/xsessions/ without the .desktop suffix. if there is a file named lubuntu.desktop, could you post the content of that file (you can leave the translations if the file is very big, but the most interesting line is Exec= and TryExec=

in any case it would be nice if you would give me the name of the file for the lxqt session, so I can add this one in the postinstall script.

Update:
I fixed it. I'm not sure why it broke with the newest update, but the big thing that changed was #3642 , so I went in and commented out the new feature.

So, this version of Lubuntu doesn't want to pass the shell as an environment variable? I'm not sure what it is about this distro/version that would break this feature.

[akarl10]

@johntdavis84 thanks for bringing this issue up. I was fooled to think it works because on plasma there seems to be no difference even tough DESKTOP_SESSION was not correctly set. I found the issue (also there is a missing \ in #3642). When I find time I will fix this in my package and make a PR for that.

[johntdavis84]

@johntdavis84 thanks for bringing this issue up. I was fooled to think it works because on plasma there seems to be no difference even tough DESKTOP_SESSION was not correctly set. I found the issue (also there is a missing \ in #3642). When I find time I will fix this in my package and make a PR for that.

You're welcome. I'm glad I helped find a bug that can be easily (?) fixed. :)

[johntdavis84]

@johntdavis84 thanks for bringing this issue up. I was fooled to think it works because on plasma there seems to be no difference even tough DESKTOP_SESSION was not correctly set. I found the issue (also there is a missing \ in #3642). When I find time I will fix this in my package and make a PR for that.

Happy New Year!

I just noticed there was an update for this package availale via apt.
I let it overwrite my custom sesman.ini with the new default one, and everything appears to be working correctly. I'm in the correct Lubuntu session.

Thanks for this. :)

Does it fix anything else?

[jsorg71]

For libva(Intel, AMD, etc) encoding I'm working on a library call libva_inf. It's partially working and once it's done we can enable hardware accel with libva. libva_inf is to replace lbyami_inf from the mainline_merge stuff. It uses libva directly and does not need libyami because libyami is archived.
Also, LK has made progress with the GFX bulk compressor so hopefully that will be coming soon too.

[Nexarian]

I did get Intel working with mainline_merge once upon a time, but I think what Jay said here is going to be better longer term. Intel redid their driver ecosystem shortly after I got it working :head_desk: