2010/8/13 Duzenbury, Rich <rduzenb...@biltd.com>:
> Ok, this is of course better.  I have no understanding of the xrdp codebase, 
> and I just wanted to get it to compile, so I hacked over this particular 
> problem.  Any idea why the debug version shouldn't already compile out of the 
> box?  Just a small oversight, perhaps?

I simply think that someone forget to commit such lines :)

> Ok, I think I understand this part now. /etc/xrdp/xrdp.ini defines the list 
> of possible options that are presented at login time.  Yesterday, I did 
> compile and install X11rdp as part of testing every way I could think of to 
> get mstsc + xrdp to work.

yes, xrdp.ini defines which backend to use. Also sesman.ini define how
should be called such beckend.

> I'm running SuSE Enterprise 10.3, I don't have a vncserver package to 
> install, however, I do have tightvnc and xorg-x11-Xvnc.  They are installed, 
> and they appear to be operational.  As I mentioned, I can use the rdesktop 
> RDP client from Ubuntu Hardy to connect to this server, and I can get 
> connected, and I can log in and use the system just fine.
>
> Here is a pstree of a successful session, via rdesktop+Xvnc
> [CUT]
> And one of a successful session, via rdesktop+X11rdp
> [CUT]

ok, seems to work fine. You have successfully installed both type of backends.

> Here are the seemingly relevant package details:
>
> rpm -qa | grep vnc
> tightvnc-1.2.9-201.17
> kdenetwork3-vnc-3.5.1-32.24
> xorg-x11-Xvnc-6.9.0-50.65.7

xorg-x11-Xvnc is the equivalent of CentOS's vnc-server-4.1.2-14.el5_3.1.i386.rpm

> So, I guess the question becomes, how can I further troubleshoot the issue?  
> The log files I am getting are sparse, they only indicate like so, even on 
> failure.:

Ok, at this point it seems to be a xrdp problem (not sesman problem).
I suggest you (as you compiled all with --enable-xrdpdebug) to run
xrdp in foreground (./xrdp -nodaemon >> logfile) to see what's
happening.

Note1: xrdp-sesman.log is actually only written by sesman, so is
sesman log only!
Note2: xrdp -nodaemon will generate a *huge* log file writing down
every function called and what is happening inside.

--
Nicola

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
xrdp-devel mailing list
xrdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xrdp-devel

Reply via email to