Replies: 9 comments 8 replies
-
|
Hi @trleith
I hope that's useful. Please come back to me after you've read it, and we'll see what we can do. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks so much. I have to digest it. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Many thanks to matt335672. I hope I've got all this right. RecapI'm trying to set up xrdp on Ubuntu 24.04 to enable remote access to a GNOME desktop with GPU rendering enabled. My goal is to utilize the NVIDIA GTX 1060 for rendering GNOME and other applications like DaVinci Resolve, while also making the GPU available for Plex transcoding, ffmpeg encoding, and Folding@Home computations. I think I've done everything correctly (again, tyro more than two decades on). I'm still facing issues. Below, I've provided an overview of my environment, configuration, and the errors I'm encountering. If this turns out to be a problem with Canonical's configuration management or a problem solvable only by local compilation, or by using "special" apt repositories and the like, I'm going to declare it infeasible for myself. However, I might possibly have enough *ix fu to gather more information for the devs, if it's useful -- I'm getting that what I want to do isn't really supported by xrdp and there are no plans. But if it is useful, just tell me how -- it's the least I can do for having all this free software. Troubleshooting StepsFollowing advice pointed-to by matt335672:
QuestionsThe consistent crashing of Xorg due to undefined symbol rdpRRModeDestroy suggests a deeper issue, possibly with the module versions or Canonical's packaging.
Environment DetailsO/S Versionxrdp and xorgxrdp Versions:$ apt policy xrdp
xrdp:
Installed: 0.9.24-4
Candidate: 0.9.24-4
Version table:
*** 0.9.24-4 500
500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
100 /var/lib/dpkg/status
$ apt policy xorgxrdp
xorgxrdp:
Installed: 1:0.9.19-1
Candidate: 1:0.9.19-1
Version table:
*** 1:0.9.19-1 500
500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
100 /var/lib/dpkg/status
ConfigurationNote: Logs have been trimmed for brevity. Full logs are available upon request I've configured xrdp to use the /etc/X11/xrdp/xorg.conf:/etc/xrdp/startwm.sh (simplified): export DISPLAY=:11
export __GLX_VENDOR_LIBRARY_NAME=nvidia
export LIBGL_ALWAYS_INDIRECT=0
gnome-shell --replaceProblem DescriptionUpon attempting to connect via RDP, I encounter a blue screen with a popup, and the session fails to start properly. Logs indicate that Xorg crashes due to undefined symbols in the From /tmp/gnome-start.log:From ./.xorgxrdp.11.log (latest run):From /var/log/xrdp-sesman.log: |
Beta Was this translation helpful? Give feedback.
-
|
xorgxrdp is still trying to use the NVidia driver. This won't work on mainline releases. Can you try the making the change detailed in neutrinolabs/xorgxrdp#241 to |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Let's see whether I've understood correctly OutcomeBlue screen. The sudo vi /etc/X11/xrdp/xorg.confsudo cat
|
Beta Was this translation helpful? Give feedback.
-
|
As you've got the NVidia drivers installed on your system, you can expect difficulties I'm afraid. The NVidia driver has its own implementation of the XRANDR extension. In the branch builds we have which work with NVidia, we have to build xorgxrdp with a switch to work around this. Bits of the NVidia stack are being loaded, despite the changes you have made:- This is down to a file in PR #1606 may have a solution for you. You need to stop the X server looking in I'm sorry I can't be more help than that at the moment. Next week I'll have access to more resources, but hopefully we can get somewhere before then. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thank you for reviewing my test results with You got me to look at this (although I would never have guessed what it's for): My ReadI think you're saying the NVIDIA driver loads because XOrg looks at its standard config paths (e.g., My interpretation is that Proposed Config ChangesReading PR#1606 I understand you to mean:
Questions
|
Beta Was this translation helpful? Give feedback.
-
|
You're nearly there I think. The following is what I have in mind:- you don't need to create a sub-directory of You shouldn't need to change anything which will affect the video card working on the console at all. You're right in that we should have two configurations - one for the RDP session and one for the console. I don't understand this:-
xrdp doesn't let you remote a local video card. Am I misunderstanding something, or not explaining it correctly? |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
So just tell it the configuration directory and let it figure everything else out. Great. I was less than clear with "If I ever wanted to have a graphical head..." I should be able to run the experiment tomorrow sometime. Thanks again, |
Beta Was this translation helpful? Give feedback.
-
|
OK - I understand now. Thanks for the clarification. Please let me know what happens with a different configuration. |
Beta Was this translation helpful? Give feedback.
-
|
Well, it took me a few days. Blue screen again. Session LogSession Manager LogWindow Manager LogWindow Manager Startup ScriptBecause I'm becoming happy with it |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I've failed to reproduce this on my system, but I believe I've found the cause of the problem. It's essentially a reading comprehension failure on my part. Your Can you try that instead? You can also revert the changes to As I've mentioned before:-
Hopefully this will help. |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Same symptom. NVIDIA Not in /etc/X11/xrdp/xorg.conf DRMAllowListShould it be? Switch to VNC?If we can't make xrdp v0.9.x work with NVIDIA, would it help to switch to VNC? Session Log**Edit: with verbose rather than debug logging |
Beta Was this translation helpful? Give feedback.
-
|
What happens when you run the X server directly? The contents of The VNC backend should work fine, but you'll need to test it meets your use-cases. |
Beta Was this translation helpful? Give feedback.
-
|
From what I read, VNC presupposes "low latency" -- I'd wanted to let my brother a couple hundred miles away use the server. We'll have to see how it acts if we end up there. I'm told Wayland isn't ready for a non-specialist like me. I hadn't heard of VNC or Wayland until a couple weeks ago; my knowledge is dated as well as limited. I'd forgotten about ~/.xorgxrdp.11.log -- I'll get it added to the startwm.sh verbose output. Console OutputRDP Session LogMissing symbols. |
Beta Was this translation helpful? Give feedback.
-
|
Tracing the undefined symbols back leads to this one at the root:- The other undefined symbol errors all result from this one. This behaviour was fixed in neutrinolabs/xorgxrdp#295 which wasn't part of the v0.9.x series. Can you try this:-
Then see if Xorg can be started from the command line using the command in this post If necessary we can get the "VNC backend" working with xrdp. That uses |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Success! At least I have a remote desktop now. It's slow, but it's there. When I launch apps (terminal, file manager, ...) they don't seem to open. nvidia-smi shows it running on the GPU. My understanding is this GPU doesn't have the most advanced scheduling, and the compute job (FahCore_26 ) is pretty demanding. The process that feeds the GPU is as nice as it can be (-19). I have no idea whether this is a problem for now -- it might be. I'll stop the job and re-test. This is promising. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
xrdp Ignores Custom
startwm.shfor Xorg Session on Ubuntu 24.04 with NVIDIA GPUHi xrdp folks, I’m fumbling through a home server setup on Ubuntu 24.04. I’ve been wrestling with xrdp to get a remote desktop working with my NVIDIA GTX 1060 (driver 550.120), and I’m stuck. This is deeper than my meager *nix/X11/sysadmin skills now disused for 25 years can handle—I need help!
##Goal (no idea why this isn't a proper heading)
A headless server (CLI-only console via
multi-user.target) with an X11-based remote desktop (GNOME) compatible with Windows Remote Desktop Connection Manager, using the GPU for rendering as well as other tasks.Problem
XRDP (0.9.24-4) won’t run my custom
/etc/xrdp/startwm.shto start Xorg and GNOME, even when set asDefaultWindowManager,UserWindowManager, or viaxrdp.ini’scommand. It keeps launching its default Xorg (e.g.,:11 -auth .Xauthority -config xrdp/xorg.conf ...), which fails with/dev/tty0permission errors, leaving me with a blue screen.Background
The GPU had been working fine for video transcoding and Folding@Home using the headless version 550 NVIDIA driver package. Iapt installedGNOME and realized I'd need the full 550 NVIDIA package. I got that replaced, and GNOME popped up on the console. OK, that proves something's working. But it turned out X11 was using the VESA driver (Nouveau had been disabled from the git-go for the sake of my other two GPU applications). I was able to get an xrdp session on my laptop. Now I want to enable rendering on the GPU and serve that over xrdp to my laptop.Let's be more precise. Or correct.
The GPU had been working fine for video transcoding and Folding@Home using the headless version 550 NVIDIA driver package. I
apt installedGNOME and GNOME popped up on the console. OK, that proves something's working. I was able to get an xrdp session on my laptop. But it turned out X11 was using the VESA driver (Nouveau had been disabled from the git-go for the sake of my other two GPU applications). What's wrong? I realized I'd need the full 550 NVIDIA package. I got that replaced and then couldn't get an xrdp session on my laptop anymore.Current State
multi-user.target(no console GUI).xrdp 0.9.24-4,xorgxrdp 0.9.19-1(stock).nvidia-smiconfirms)./etc/X11/Xwrapper.config: allowed_users=anybody/etc/xrdp/xrdp.ini/etc/xrdp/sesman.ini/etc/xrdp/startwm.shxrdp.log(latest attempt, April 4, 2025, ~18:15 CST, during blue screen)loginctl_list-sessions output(latest attempt, April 4, 2025, ~18:15 CST, during blue screen):-- I had an SSH session, that's
Type=ttyfortrl-- no
x11—Xorg fails too fast to register--
/tmp/.X11-unix/empty--
ps aux | grep Xorgshows no Xorg processes-- no
/tmp/startwm.log(demonstrates startwm.sh never ran at all)What I Tried
Worked pre-NVIDIA with VESA, broke after NVIDIA 550 install. X11 and xrdp worked with the VESA driver; don't work with the full NVIDIA 550 driver package.allowed_users=anybody—no effect on default Xorg crash.startwm.sh: Added NVIDIA vars and manual Xorg launch—never runs.[Xorg], setDefaultWindowManagerandUserWindowManager(full paths)—xrdp apparently ignores them.xrdp.iniCustomSession: Login box showsCustomSession, but no desktop—script still skipped.logindsees it asx11.Why Not #3470?
I considered Issue #3470 ("Can't log in, but don't get any errors"), but it doesn’t fit:
If you wait long enough a window titled "Connection Log" pops up on the blue screen. The contents are as follows:
connected ok), no desktop—implies a hang without X server failure.no X server active), andstartwm.shis bypassed—logs and client "Connection Log" show a clear crash./dev/tty0errors (from past Xorg logs) and lack of/tmp/startwm.logpoint to XRDP ignoring our script, not a silent stall like 3470.I’m at a loss.
Question
startwm.shrunning despiteDefaultWindowManager,UserWindowManager, orcommandsettings in the current state?I absolutely can provide more information -- just tell me what. This is all I can think of.
My thanks to anyone who's read this far.
Beta Was this translation helpful? Give feedback.
All reactions