Replies: 12 comments 17 replies
-
|
Most likely thing is you haven't specified a path to Xorg in |
Beta Was this translation helpful? Give feedback.
-
|
I had already edited seman.ini to provide the full path to Xorg. |
Beta Was this translation helpful? Give feedback.
-
|
Was that successful? |
Beta Was this translation helpful? Give feedback.
-
|
As I said; I had already done that step as part of my initial setup before attempting to connect. As such, there was nothing for me to change. I don't know if it matters, but this is the only change I had made to sesman.ini. |
Beta Was this translation helpful? Give feedback.
-
|
OK - sorry I missed that. The X server should be starting then. Can you have a look in |
Beta Was this translation helpful? Give feedback.
-
|
I generated fresh logs to be sure; this is the first mention of RandR and everything that followed: |
Beta Was this translation helpful? Give feedback.
-
|
We had a fix for the RandR input problem a while ago:- Your initial report doesn't seem consistent with this however. If the screen resize is being generated, it's likely a connection has been made. Can you check the |
Beta Was this translation helpful? Give feedback.
-
|
This is the xrdp-sesman.log from the attempt referenced in the previous log! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. It looks to me like your xorgxrdp is missing neutrinolabs/xorgxrdp#254 Log in to the box over ssh and run this command:- Hit CTRL-Z and type the command Then see what the command After that, kill the X server by using |
Beta Was this translation helpful? Give feedback.
-
|
I do have xorgxrdp logs for display 10 (I built and installed from source, v0.10.1). Interestingly, your experiment yielded this: |
Beta Was this translation helpful? Give feedback.
-
|
I removed .Xauthority and replaced it with a symlink to $XAUTHORITY. This seems to fix your test, but, for some reason, the symlink gets removed and replaced with a file, this, resulting in the output I referenced just above. Now, if I login via console (which I won't have long term; this is a headless machine) and recreate the symlink... Then, I logged off the console, and the output above remains the same. I then I verify the .Xauthority file, which is still a symlink. I then attempted to access the machine via RDP and it failed with the original error and .Xauthority had been replaced. Perhaps worth noting, but I explicity did not include an XAUTHORITY override in my .xsessionrc: |
Beta Was this translation helpful? Give feedback.
-
|
Overriding XAUTHORITY won't work - see #2417 That all looks OK to me. Starting Xorg in that way gives you an XrandR output which you can see in the output. This is a bit of a mystery at the moment, made more difficult as I can't be sure exactly what you've built and installed. It certainly looks like neutrinolabs/xorgxrdp#254. Let's try to get this test working properly. Here's a script for you. You may need to change the path in the WAITFORX= line depending on where xrdp is installed:- #!/bin/sh
WAITFORX=/usr/local/libexec/xrdp/waitforx
export DISPLAY=:11
unset XAUTHORITY
rm -f .Xauthority
/usr/lib/xorg/Xorg $DISPLAY -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log > /dev/null 2>&1 &
XORG_PID=$!
xrandr
$WAITFORX -d $DISPLAY
kill $XORG_PID
wait
grep SetRdpOutputs .xorgxrdp.${DISPLAY#:}.logSee what that gives you. |
Beta Was this translation helpful? Give feedback.
-
|
As for what was built/installed: I downloaded the latest releases for both xorgxrdp and xrdp. XRDP configure command: As for the script, I made a few small changes. #!/bin/bash
WAITFORX=/usr/local/libexec/xrdp/waitforx
export DISPLAY=:11
cd ~
unset XAUTHORITY
rm -f .Xauthority
echo "Starting Xorg on display ${DISPLAY}"
/usr/lib/xorg/Xorg $DISPLAY -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log > /dev/null 2>&1 &
XORG_PID=$!
echo "Xorg started with pid ${XORG_PID}"
echo "Executing xrandr"
xrandr -d $DISPLAY
echo "Running ${WAITFORX} -d ${DISPLAY}"
$WAITFORX -d $DISPLAY
RESULT=$?
echo "waitforx RC=${RESULT}"
echo "Killing ${XORG_PID}"
kill $XORG_PID
wait $XORG_PID
RESULT=$?
echo "Xorg RC=${RESULT}"
grep SetRdpOutputs .xorgxrdp.${DISPLAY#:}.log
exit $?The script hangs on executing xrandr, and eventually this is the output: |
Beta Was this translation helpful? Give feedback.
-
|
The hang sounds like a race which suggests the X server is taking longer to start than perhaps it should. Can you post the whole |
Beta Was this translation helpful? Give feedback.
-
|
What is strange is the symlink trick does allow xrandr to open the display (after the xrdp process is started; it overwrites it on startup). I could try doing the symlink trick and then connecting to the main XRDP process, but first, the test you requested! |
Beta Was this translation helpful? Give feedback.
-
|
I can see a huge hang in the Xorg log file before this message:- You might have some stale lock files which are causing this. What do you get after running the script for |
Beta Was this translation helpful? Give feedback.
-
|
The script removes the file and it seems to fail to recreated when it's not present. I modified the test script to |
Beta Was this translation helpful? Give feedback.
-
|
@isaki - I can't understand why you want to add a symlink. Where is this symlink pointing? |
Beta Was this translation helpful? Give feedback.
-
|
It was only a troubleshooting step I did (that solves the issue, at least for the tests you've proposed) by pointing to the value stored in the ENV's XAUTHORITY variable when logged in via the remote console. Obviously, this is not a valid long term solution as the code functions today, since it removes the symlink (and requires me to log into the console, which, is not something I will be able to do long term). |
Beta Was this translation helpful? Give feedback.
-
|
OK - thanks. Possibly a silly question - is the HOME directory for the user writeable by the user? |
Beta Was this translation helpful? Give feedback.
-
|
It is indeed! I'm sorry for the slow reply; I've been really busy and haven't had time to focus on this! |
Beta Was this translation helpful? Give feedback.
-
|
Slow replies are fine - most of our users are busy people! This smells like an environment problem to me. What do you get for :- Also, try running the script with a clean environment (i.e.):- |
Beta Was this translation helpful? Give feedback.
-
|
Here are the results you asked for! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. The xauthority file seems to be a bit of a rabbit-hole which I think we need to climb out of. Let's edit the test file to work more like xrdp does. Can you add this line to Also, move the Then try running the file. Post the output from that, and also post the contents of |
Beta Was this translation helpful? Give feedback.
-
|
Updated script: #!/bin/bash
WAITFORX=/usr/local/libexec/xrdp/waitforx
export DISPLAY=:11
cd ~
unset XAUTHORITY
rm -f .Xauthority
xauth add $DISPLAY . 0123456789ABCDEF
if [ $? -ne 0 ]; then
echo "xauth add command failed"
fi
echo "Starting Xorg on display ${DISPLAY}"
/usr/lib/xorg/Xorg $DISPLAY -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log > /dev/null 2>&1 &
XORG_PID=$!
echo "Xorg started with pid ${XORG_PID}"
echo "Running ${WAITFORX} -d ${DISPLAY}"
$WAITFORX -d $DISPLAY
RESULT=$?
echo "waitforx RC=${RESULT}"
echo "Executing xrandr"
xrandr -d $DISPLAY
RESULT=$?
echo "xrandr RC= ${RESULT}"
echo "Killing ${XORG_PID}"
kill $XORG_PID
wait $XORG_PID
RESULT=$?
echo "Xorg RC=${RESULT}"
grep SetRdpOutputs .xorgxrdp.${DISPLAY#:}.log
exit $?Execution output: The log you requested: |
Beta Was this translation helpful? Give feedback.
-
|
That all looks absolutely fine to me. Given that's what xrdp actualy does, I can't see where the problem could be at the moment. Can you create a new user on the system with a default configuration and see if that works? |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I am using the 0.10 version in ubuntu 22.04, i get the same issues now |
Beta Was this translation helpful? Give feedback.
-
|
i run the above command , here is the log file: [ 1688.581] Current Operating System: Linux US-NORMANC2-LNX 6.8.0-47-generic #47 [ 1688.585] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration |
Beta Was this translation helpful? Give feedback.
-
Greetings,
I have installed (from source) xrdp 0.10 and xorgxrdp 0.10.1. I am able to connect to xrdp, however, after some time, I get a warning window that the X server could not be started (and the ability to log into xrdp once again, so I am getting display output).
I am running Ubuntu 22.04 LTS.
The only error that I can seem to find is in the system log:
Has anyone seen this before, and if so, is there a trick to fixing it? I was using 0.9.24 on this system previously (I'd get a blank screen for 60 seconds, then I'd get my desktop), but the NVMe failed and I had to do a clean install of everything, so it's entirely possible I've missed something important in my rush to get this system working again.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions