xrdp with egfx pipeline testrun #2383
Replies: 33 comments 50 replies
-
|
this greatly reduces cpu usage under WSL |
Beta Was this translation helpful? Give feedback.
-
|
Hi
im think SSL_write: I/O error is a main problem, i'm trying to search this error, but don't find working solution
if you catch this error and have a solution, tell me please |
Beta Was this translation helpful? Give feedback.
-
|
have you restarted xrdp or the machine after switching from xrdp to xrdp-egfx? do you have another client you could test with? |
Beta Was this translation helpful? Give feedback.
-
|
ok, found the issue... you must set the color depth to 32 in mstsc. |
Beta Was this translation helpful? Give feedback.
-
|
in mstsc....wow...its really fix that! right now its works, thank you so much! |
Beta Was this translation helpful? Give feedback.
-
|
this issue is now fixed in my ppa. I also notified someone on gitter, so I think they will work out a appropriate solution. |
Beta Was this translation helpful? Give feedback.
-
|
I am having some issues with this that I don't really understand : I'm trying to connect with Remmina, in case that matters. The client just gets a black screen. |
Beta Was this translation helpful? Give feedback.
-
I don't know.. This ppa is compiled without cuda
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)
sorry about that. if you manually rm -rf /etc/X11/xrdp the deinstallation should continue.. |
Beta Was this translation helpful? Give feedback.
-
|
Also tried with a Xubuntu 22.04.1 install, updated. That seems to give the same kind of results. Logs attached. |
Beta Was this translation helpful? Give feedback.
-
this time the error is different. Xorg does not start. see ~/.xorgxrdp.10.log |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
hmm, maybe the nvidia driver itself has a issue.. 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 |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if I did this right, but it's still really slow for me I connect with remmina and I can watch it paint the screen line by line (connected via 10Mbps connection) |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
Here's a fun one, I migrated our production xRDP server to use egfx, with the following commands: 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: |
Beta Was this translation helpful? Give feedback.
-
|
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: if a user wants to set its own he should put (example with plasma) in ~/.profile |
Beta Was this translation helpful? Give feedback.
-
|
sigh...sorry for jumping over the doc |
Beta Was this translation helpful? Give feedback.
-
|
How does this relate to dri3/glamor hardware acceleration in xrdp (that is working stable for me) ? #1029 |
Beta Was this translation helpful? Give feedback.
-
|
Wow this is really impressive. Thanks for your work all. 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? client: xrdp.log: |
Beta Was this translation helpful? Give feedback.
-
|
Multimonitor is still a work in progress for EGFX! |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Clean install , does not work at debian =) but still cannot install via apt-add-repository ppa:saxl/xrdp-egfx any ideas how to install that ? |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
I'm not using multiple sessions. I just wanted to have this flag enabled to avoid black-screen when I forget to logout locally Problem described above happens for with just me logged in once over rdp. |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
I am very intrigued. Would an aging Nvidia Quadro P2000 be able to accelerate this? |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
egfx got merged already with the exception of h264. I might update my ppa if @Nexarian can tell me what the best testdrive branch would be |
Beta Was this translation helpful? Give feedback.
-
|
So there have been multiple titanic shifts in the underlying code of the Then we did a major push to integrate the basic framework of So instead my plan is to rebuild I should be able to start work on that with a target finish by end of March 🤞 |
Beta Was this translation helpful? Give feedback.
-
|
How goes the progress for nVidia? |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to build this on Alpine? |
Beta Was this translation helpful? Give feedback.
-
|
Try it and share the result! |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
are you running it in a container? |
Beta Was this translation helpful? Give feedback.
-
|
Hi Team Want to take a minute to express my gratitude for this work and how it has positively impacted me and homelab experience; I definitely look forward to the merge mentioned above. I am currently running Proxmox on some older enterprise hardware and running an LXC container with Ubuntu and KDE installed. Thanks to this work I am able to pass through my 3060 12GB GPU, remote in, and have an exceptional / smooth buttery UI GPU accelerated experience while developing remotely (still some kinks with the LXC based desktop configuration and I am at best a novice but it works okay). As a tangent, on account of the GPU pass through I can use LM Studio to host multiple quantized LLMs (i.e. DeepSeek Coder, Llama 3 instruct) and with the right plugins in VS Code (i.e. Twinny, Continue) can interface to coding LLMs to speed up work (all local based inferencing). Add in Tailscale and I can pretty much remote in from anywhere and pickup work efficiently; It's just so gorgeous and an exceptional lightweight experience. Thank you! I would like to share one observation/bug from using different RDP clients. I have tested this with Apache Guacamole (freeRDP I believe) and multiple Android RDP clients and there's a recurring theme that when you connect, you can access the XRDP login screen, however after entering credentials the desktop does not render and just stays blacks. Something is happening on the screen, as the cursor changes when you move around, but it still stays black. I have aggressively played around with client RDP options, but have not had success. I am more than happy to troubleshoot and share any logs; I would appreciate any guidance on where or how to start looking to support identifying the underlying issue. Thank you again! |
Beta Was this translation helpful? Give feedback.
-
|
@standas Could you open a separate issue for your issue? There's an issue report form. |
Beta Was this translation helpful? Give feedback.
-
|
Absolutely. As this is only specific to this patched release (not v0.10.0) assume I would use the following to create the issue? 
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, any news for Ubuntu noble? |
Beta Was this translation helpful? Give feedback.
-
|
A new package for noble is landed. This however is based on upstream with software h264 encoding enabled. There is no special nvidia support since that branch is not updated for some time and there seem to be some compatibility issues with newer mstsc. |
Beta Was this translation helpful? Give feedback.
-
|
Hello! Thanks again for all your work on this. I've been using it with Proxmox 8.2.2 and Intel iGPU passthrough to a Lubuntu 22.04 VM via SR-IOV. I've noticed that the only resolution available inside the VM via xrdp is 2048x1152 at 25 fps on rdp0 and rdp1 (I currently have dual monitors running in full screen on the client side, which is equipped with two LG Ultrafine 4K monitors). "Screen 0" is 4096 x 1152--I assume this is a dummy driver type thing to get the Xorg server to start properly before I log in. Is there a reason its locked to this resolution? I wanted to ask before I tried it in case the current resolution is a limitation of the current implementation of xrdp. |
Beta Was this translation helpful? Give feedback.
-
|
First of all, thank you for your work. Now I try to connect to xrdp using freerdp and enable nvidia's h264 encoding acceleration feature.
Looking at the log, there are several places where errors occur, xorgxrdpWrapPreIntScreenInit function and xf86EnableIO function. ps.
but I bypassed that by adding the user to the tty group and setting the tty permissions to group readable. Operating environment: ubuntu 22, xorg 21.1.4, dual graphics cards: intel card0, nvidia card1). |
Beta Was this translation helpful? Give feedback.
-
|
@akarl10 I am using Remmina and manage to connect my GCP VM. |
Beta Was this translation helpful? Give feedback.
-
|
what version of ubuntu are you using? The package for 24.04 does currently have no nvidia support. generally there are two areas where a gpu can help: h264 encoding (you where using rfx pro, so no help from the gpu there) and "generic" desktop 3d acceleration (i.e. launch of a opengl or vulkan application in the rdp session). To be honest if available I would prefer anything but nvidia for that usecase (I know the performance might be the best with nvidia and cuda might also be a limiting factor). Practically every gpu except nvidia uses the mesa/kms stack to do 3d rendering and that works with way less issues inside of xrdp. The only thing that is really missing (at least in this ppa) is 264 hw encoding for mesa/vaapi another thing to consider is that ubuntu's rdp clients have no h264 gfx support (probably license issues, but don't quote me on that). Using a flatpak version might not have that issue. I usually use a locally compiled version or thincast rdp |
Beta Was this translation helpful? Give feedback.
-
|
Hello! Thanks again for this. I couldn't do any actual VDI work on my home Proxmox cluster without it (using an i7-12700T's iGPU with SR-IOV passthrough). :) I had a question. According to this issue, "GFX graphics" has been implemented into the mainline xrdp package v. 0.10.0: #1422 How does that compare to the xrdp-egfx package, which is at 0.2.22.20230831 in the PPA (Lubuntu variant, in my case, on 22.04 Jammy)? That is, would I get better performance/more bugfixes in mainline xrdp at this point, or am I still better off sticking with xrdp-egfx? This could also be a moot point, as Jammy doesn't offer mainline xrdp version 0.10... (I apologize if this is an obvious question. I tried looking at the currently extant issues tracking development, and got pretty confused.) |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I'm still using this PPA for hardware accelerated Microsoft Remote Desktop access with an Ubuntu 22.04 VM. I noticed that there's a new note at the top of this page:
My 22.04 VM will be rolling over to 24.04 soon. At this point I'm still pretty confused about when I'd want to stick with this package vs. using the upstream one. I think Microsoft Remote Desktop, for instance, uses H.264, so I'd want to keep using this package? Also, will the official package reach feature parity with this offshoot at some point, such that this PPA won't be maintained anymore? |
Beta Was this translation helpful? Give feedback.
-
|
I would hope that the official package will eventually reach feature parity. Also strangely ubuntu did not patch the package/startwm.sh in a way that it launches gnome/ubuntu by default whereas this package contains some modification that should make this work oob, to saying though that the way I did that is the best approach (see desktop selection above. When installing the package pre-fills this environment variable according to a list of known desktops and installed desktops). To be honest I was never in contact with them to discuss how this could be improved tough |
Beta Was this translation helpful? Give feedback.
-
|
Tried to reply by email and it didn't work quite like I hoped it would. Replied to at #2383 (comment) . |
Beta Was this translation helpful? Give feedback.
-
|
Hello!
Thanks for the reply, and the clarification on the difference between the packages. Sounds like I’ll need to stick with this repo a bit longer. I’m so glad it’s here; I couldn’t use my Intel iGPU for GPU-accelerated Remote Desktop with my Ubuntu virtual machines any other way.
As far as I know, this is the only Remote Desktop package for Debian/Ubuntu that just works with GPU HW acceleration over VA-API (using the non-free Intel VA-API package). I’ve never gotten NoMachine or Sunshine to work right with it. I also never got sound working with the xrdp in the distro repo. I’m so glad this project is here. :)
(Apparently, there’s some proprietary Remote Desktop thing in GNOME that “just works” out of the box with Intel iGPUs, but I’m not a GNOME user…)
I’m using Ubuntu 22.04 Jammy still in this VM, and noticed that the distro repo version of xrdp is at:
xrdp/jammy 0.9.17-2ubuntu2
xorgxrdp/jammy 1:0.2.17-1build1
This repo’s version is listed as:
xrdp-egfx/jammy,now 0.9.22.20230831-1ubuntu1+0egfx1~jammy
xorgxrdp-egfx/jammy,now 1:0.9.22.20230831-1ubuntu1+0egfx2~jammy
pulseaudio-module-xrdp/jammy,now 0.6-1prebuild0~0jammy6
Are there newer versions in either repo for 24.04? The addendum to the readme confused me a bit.
Also, at least on Jammy, I don’t seem to have a pipewire module available anywhere.
***@***.***:~$ apt search pipewire-module-xrdp
Sorting... Done
Full Text Search... Done
… On Feb 24, 2025, at 10:05 AM, akarl10 ***@***.***> wrote:
I would hope that the official package will eventually reach feature parity.
As for suggestions what package to use: This one is slightly newer than the one shipped with ubuntu, mainly the one from ubuntu is still from 0.9 branch so it does not have egfx (that is either rfx progressive or h264) but only rfx and "old" gdi.
Also strangely ubuntu did not patch the package/startwm.sh in a way that it launches gnome/ubuntu by default whereas this package contains some modification that should make this work oob, to saying though that the way I did that is the best approach (see desktop selection above. When installing the package pre-fills this environment variable according to a list of known desktops and installed desktops).
To be honest I was never in contact with them to discuss how this could be improved tough
—
Reply to this email directly, view it on GitHub <#2383 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGI5CYSGU4SFWPOHYOKAMHD2RM7OLAVCNFSM6AAAAAAQ42SA4KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZQGI3TCMQ>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
the versioning scheme is more or less the "nearest" release version + yyyyMMdd date stamp of the git repository. on https://launchpad.net/~saxl/+archive/ubuntu/xrdp-egfx |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the clarification. I wasn’t aware the launchpad site let you browse and version-filter like that. Really awesome.
I look forward to being able to finally get my VMs on 24.04 so I can get the newest one.
Will there be another branch change whenever Ubuntu 24.10 comes out? I’m guessing not, since it seems like the current branch is in maintenance mode (everything’s working and being integrated into the main package over time)?
… On Feb 25, 2025, at 1:11 AM, akarl10 ***@***.***> wrote:
the versioning scheme is more or less the "nearest" release version + yyyyMMdd date stamp of the git repository.
for 22.04 the git repository used was the nexarian branch, whereas 24.04 is based on the devel branch.
on
https://launchpad.net/~saxl/+archive/ubuntu/xrdp-egfx
you can see each version for each distribution version
—
Reply to this email directly, view it on GitHub <#2383 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGI5CYR4KENZ6GUQ5KU6L3D2RQJRHAVCNFSM6AAAAAAQ42SA4KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMZQHEZTOMI>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
|
Hey guys, I updated the xrdp-egfx build script a bit. |
Beta Was this translation helpful? Give feedback.
-
|
@tabletseeker I don't know if you noticed, there is a branch in github.com/jsorg71/builders called iHD that builds iHD with the rest. Don't know if it will be of any use. If I remember right, you enable it with --enable-iHD. |
Beta Was this translation helpful? Give feedback.
-
|
@jsorg71 As far as I can tell, all you need for xrdp are the following packages: Here is the buildyami.sh I forked: |
Beta Was this translation helpful? Give feedback.
-
|
Is that the non-free (contained non-FOSS bits, I think?) intel media driver from the repo, as opposed to the free one from the repo?
At one point the free driver didn’t fully enable the necessary hardware acceleration.
… On Mar 11, 2025, at 1:40 PM, tabletseeker ***@***.***> wrote:
$jsorg71
Hey man, yeah I saw that. It builds the same stuff, but I guess we can scratch the discontinued vaapi driver and only use the intel-media-driver which is probably what you mean by iHD.
Other than that the scripts are identical, apart from dependencies and some minor updates missing in yours since its a bit dated.
As far as I can tell, all you need for xrdp are the following packages:
LIBDRM="2.4.124"
LIBVA="2.22.0"
LIBVAUTILS="2.22.0"
INTEL_MEDIA_DRIVER="24.4.4"
LIBVA_INTEL="2.4.1"
INTEL_GMMLIB="22.7.0"
—
Reply to this email directly, view it on GitHub <#2383 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGI5CYVKU4YB3UT3NSR3M6T2T4UZBAVCNFSM6AAAAAAQ42SA4KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBWGU3TIMY>.
You are receiving this because you commented.
|
Beta Was this translation helpful? Give feedback.
-
Precisely. The free driver That's the one built by my script/repo. Additionally, I made some updates to enable proper use in Debian VMs. Apart from this I updated the version numbers and fixed minor stuff that breaks the build in @Nexarian's and @jsorg71's version of the xrdp build scripts. |
Beta Was this translation helpful? Give feedback.
-
|
@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 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 Inside the VM:
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? |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your reply. :)
Oh, good. That actually makes things simpler. I was afraid I hadn't configured Lubuntu or
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.
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:
So, since I've been using two displays, I haven't had the option for resolution switching.
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. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
Essentially what you see is, as you probably expected, is the compression of h264 (or maybe rfx pro). this is most notable on red color (see https://en.wikipedia.org/wiki/Chroma_subsampling, the mode used is usually 4:2:0. 4:4:4 would not have that issue but hw encoders usually don't support that. There exists a kind of 4:4:4 mode in remote desktop, but I think this is not implemented in xrdp. @jsorg71 correct me if I am wrong). what client are you using? xfreerdp as a client on ubuntu does not use h264 and falls back to rfx progressive. |
Beta Was this translation helpful? Give feedback.
-
Are you sure about that? I am using xfreerdp on debian with option
The manpage also says that gfx progressive is off by default. https://manpages.debian.org/unstable/freerdp2-x11/xfreerdp.1.en.html Is there even another xrdp client on Ubuntu or Debian that can use h264 with hw accelaration? |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
and others
-
#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.
when upgrading check if
/etc/xrdp/sesman.inicontainsSessionSockdirGroup=xrdpin the[Security]sectionThe upgrade should convert old nvidia configuration so that the session starts. In doubt apt purge xrdp-egfx xorgxrdp-egfx, remove /etc/xrdp, /etc/X11/xrdp and reinstall both packages.
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-xrdpI 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.rulesAlso 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-xrdpswap back to xrdp from xrdp-egfx
tweaks
desktop selection
The desktop that gets launched is configured in
/etc/xrdp/sesman.iniLook for the line
you can put every desktop listed in
/usr/share/xsessions. Just put the name wihout .desktopIf you want to use this feature on a per user basis you could put something like
in ~/.profile
nvidia h264 hardware encoding
if you have a nvidia gpu you might enable hardware h264 encoding by editing
/etc/xrdp/sesman.inisimply change the line at the near bottom from
# XRDP_USE_HELPER=1toXRDP_USE_HELPER=1multisession 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.inifrom# XRDP_USE_MULTISESSION=1toXRDP_USE_MULTISESSION=1Should 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 saysor
desktop 3d and video
For 3d check if
glxinfo | grep rendereroutputs 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.iniin 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 managementissues
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
Beta Was this translation helpful? Give feedback.
All reactions