xrdp with egfx pipeline testrun #2383
Replies: 41 comments 99 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.
-
|
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.
-
|
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.
-
Wait, they merged it already?
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. |
Beta Was this translation helpful? Give feedback.
-
|
@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) |
Beta Was this translation helpful? Give feedback.
-
|
@akarl10 I connect via Windows Remote Desktop (Windows 11), with xrdp-egfx-0.10.80-20241223 |
Beta Was this translation helpful? Give feedback.
-
|
@OSMaxwell you may try to disable h264 server side and only enable rfx progressive: |
Beta Was this translation helpful? Give feedback.
-
|
Is this the pull request that merged egfx? Just says |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your reply. :) I'm actually using a 12th gen i7-12700T, with the UHD 770 (UHD 750 with higher clocks). I'm not entirely sure that I'm reading it right, but looking at 4:4:4 encoding, I think it supports:
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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
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.
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.
How did you actually get useful diagnostic information out of Windows 11? :-P |
Beta Was this translation helpful? Give feedback.
-
|
Most of the bits from mainline merge have been merged to devel including most of the nvidia hack bits. It should be stable.
xrdp PRs, there are other PRs for xorgxrdp not listed here. |
Beta Was this translation helpful? Give feedback.
-
Yes, I was wondering about this. Would it be possible to simply modify the xrdp/devel Makefile and other stuff to build with
@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. |
Beta Was this translation helpful? Give feedback.
-
|
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." |
Beta Was this translation helpful? Give feedback.
-
@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 |
Beta Was this translation helpful? Give feedback.
-
|
Matt expressed interest in putting the latest libyami in our thirdparty for our use in xrdp. 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 |
Beta Was this translation helpful? Give feedback.
-
Broadly speaking, what would this pull request look like? |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I'm getting this error. I'm using it wish WSL. I have Ubuntu 24.04 and GNOME installed. 
|
Beta Was this translation helpful? Give feedback.
-
|
There are some things that you can check:
|
Beta Was this translation helpful? Give feedback.
-
|
I installed Nexarian script and tried again. It didn't work. That's what I get from the log file: |
Beta Was this translation helpful? Give feedback.
-
|
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). |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I thought my linux subsystem had access to my GPU directly. |
Beta Was this translation helpful? Give feedback.
-
|
I don't have a windows 11 machine, let alone one with a nvidia gpu, so I cannot help you there. other then that: You need someone with a windows 11 machine that can help you.. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
I actually checked the sesman log before and Idk how that hell I missed that, but here it is: |
Beta Was this translation helpful? Give feedback.
-
|
@verlox will try to release a new package tomorrow. actually there is something missing (there should be |
Beta Was this translation helpful? Give feedback.
-
|
Yeah no worries, I should actually thank you. Both for making this package and taking your time to troubleshoot this with me - No rush. |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
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: 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. |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
actually yes. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
#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 variableXRDP_USE_ACCEL_ASSIST=1in the[SessionVariables]section insesman.iniA 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.inicontainsSessionSockdirGroup=xrdpin the[Security]sectionEven 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