connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to sesman
login successful for display 10
connecting to 127.0.0.1 5910
error - problem connecting
Printed in the dialog box when attempting to connect to an XRDP enabled system.
The latter problem implies a connectivity problem, which couldn't be further from the cause.
Many sites insist that installing XRDP, vncserver (of some sort) in one order or another is the problem. Also misleading.
Then you look in xrdp-sesman-log in /var/log, you will see this
[INFO ] starting Xvnc session... [ERROR] X server for display 10 startup timeout [INFO ] starting xrdp-sessvc - xpid=3531 - wmpid=3530 [ERROR] X server for display 10 startup timeout [ERROR] another Xserver is already active on display 10 [DEBUG] aborting connection...[20130627-08:55:49] [INFO ] ++ terminated session: username root, display :10.0, session_pid 3529, \
ip 192.168.0.227:59050 - socket: 7
Indicating that somehow your RDP session has two Xservers active. What happens when you log in is that a login method is performed to authenticate, and the top dialog indicates the progress of that.
Then it will spawn some VNC server session for the X session (uses 10, 11, etc.) to connect.
If you read the symptoms here, there is already a session or server on 5910. Completely wrong.
To find the problem, one has to try running the window manager. I don't know if this would happen for other than xfce4, which I use, but it produces the root problem. run:
If you try running vncserver, you will see at the end of the startup this:
[dix] Could not init font path element /usr/share/fonts/default/Type1, removing from list! [dix] Could not init font path element built-ins, removing from list! Fatal server error: could not open default font 'fixed'
Turns out that if any failure occurs in the chain of events between the authentication after the RDP login and getting the session going, you get the " Xserver is already active on display" message in the var log sesman log.
Other errors I suspect produce the same nonsense, someone reported when the vnc server and client couldn't agree on a geometry, the same error occurred.
This is probably the solution to all the load order issues and which vnc server (real or tight) package you use.
I have solved it by installing xfonts-base
This also solved my problem.