Hi Nicola,
> No, better to know how many bytes.
>
> Use this:
>
> xrdp_tcp_send(struct xrdp_tcp* self, struct stream* s)
> {
> int len;
> len = s->end - s->data;
> DEBUG(" in xrdp_tcp_send, gota send %d bytes", len);
> if (trans_force_write_s(self->trans, s) != 0)
> {
> DEBUG(" error in trans_force_write_s"));
> return 1;
> }
> DEBUG(" out xrdp_tcp_send, sent %d bytes ok", len);
> return 0;
> }
>
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?
> This means you have not x11rdp binary on your system.
> Sesman can load 2 different component as graphical X server backend
> (not included in xrdp):
> 1. X11rdp
> 2. Xvnc
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.
>
> I suggest you to install and use vncserver (Xvnc) instead. I use
> CentOS and the rpm is: vnc-server-4.1.2-14.el5_3.1.i386.rpm
>
> Nicola
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
sesman
|-sessvc 17222 17221
| |-Xvnc :13 -geometry 1280x980 -depth 16 -rfbauth
/home/rduz/.vnc/sesman_passwd -bs -ac -nolisten tcp
| `-startwm.sh /usr/local/xrdp/startwm.sh
| `-startkde /opt/kde3/bin/startkde
| `-kwrapper ksmserver
`-{sesman}
And one of a successful session, via rdesktop+X11rdp
sesman
|-sessvc 18038 18037
| |-X11rdp :13 -geometry 1280x980 -depth 16 -bs -ac -nolisten tcp
| `-startwm.sh /usr/local/xrdp/startwm.sh
| `-startkde /opt/kde3/bin/startkde
| `-kwrapper ksmserver
`-{sesman}
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
rpm -ql xorg-x11-Xvnc
/usr/X11R6/bin/Xvnc
rpm -ql tightvnc-1.2.9-201.17
/usr/X11R6/bin/vncserver (+ many others)
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.:
[20100812-17:54:03] [INFO ] scp thread on sck 5 started successfully
[20100812-17:54:03] [INFO ] granted TS access to user cwheeler
[20100812-17:54:03] [INFO ] starting Xrdp session...
[20100812-17:54:03] [INFO ] starting sessvc - xpid=5051 - wmpid=5050
How do I enable full debug logging so I can track down what the problem is?
Thank you.
Regards,
Rich
------------------------------------------------------------------------------
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
