[FreeNX-kNX] x11 client initiated but not displaying and Problem connecting with Freenx

Leopold Palomo Avellaneda lepalom at wol.es
Wed Sep 20 21:55:27 UTC 2006


Hi,

I hope not offending trying to join to thread that I think that have similar 
problem. Both of us are trying to use free nx with a debian unstable (maybe 
etch?) boxes.

I have a server with freenx configured and patched to use the nxclient 2.0, 
but it's a debian sarge (stable) box.

My packages are:
ii  freenx         0.4.4+0.4.5-3  The FreeNX application/thin-client server ba
ii  nxagent        1.4.92+1.5.0-3 NoMachine NX - nesting X server with roundtr
ii  nxclient       2.0.0-98       NX Client
ii  nxlibs         1.4.92+1.5.0-3 NoMachine NX - common agent libraries

and the system works.

I have installed the same packages in my etch (with a lot of packages box) and 
I have the same problem as levine some times, and if I change some the 
version of the package I have this error. But I think that the error comes 
from the same place and one of the main differences of the sarge and etch: 
the xorg.

My error,


NXPROXY - Version 1.5.0

Copyright (C) 2001, 2005 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '6928'.
Info: Synchronizing local and remote caches.
Info: Handshaking with remote proxy completed.
Info: Using cache parameters 4/262144/32768KB/32768KB.
Info: Using image cache parameters 1/1/131072KB.
Info: Using modem link parameters 2048/8/40/200.
Info: Using pack method '16m-jpeg-3' with session 'unix-kde'.
Info: Using ZLIB data compression level 6.
Info: Using ZLIB data threshold set to 32.
Info: Using ZLIB stream compression level 9.
Info: Using remote ZLIB data compression level 6.
Info: Using remote ZLIB stream compression level 9.
Info: No suitable cache file found.
Info: Forwarding multimedia connections to port '32872'.
Info: Starting X protocol compression.
Info: Established X server connection.
Info: Using shared memory support in X server.
Warning: No data received from remote proxy within 33 seconds.
Error: Lost connection to peer proxy on FD#9.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.


Now, I have download the source and recompile and reinstalled a new packages 
and now I have the error:

NX> 1000 NXNODE - Version 1.4.0-45-SVN OS (GPL)
NX> 700 Session id: ranganathan-1013-C5D092E85217A304F457629302273834
NX> 705 Session display: 1013
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: bac98955f87926326dc046d1e6d5326f
NX> 702 Proxy IP: 127.0.0.1
NX> 706 Agent cookie: bac98955f87926326dc046d1e6d5326f
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 1
NX> 1004 Error: Session did not start.
NX> 504 Session startup failed.
NX> 999 Bye
Killed by signal 15.


and my /usr/X11R6 has:

$/usr/X11R6# tree
.
|-- bin -> ../bin
`-- lib
    `-- X11
        |-- fonts
        |   |-- 100dpi
        |   |   |-- fonts.alias
        |   |   `-- fonts.cache-1
        |   |-- 75dpi
        |   |   |-- fonts.alias
        |   |   `-- fonts.cache-1
        |   |-- Type1
        |   |   |-- encodings.dir
        |   |   |-- fonts.cache-1
        |   |   `-- fonts.dir
        |   |-- encodings
        |   |   |-- 
encodings.dir -> ../../../../../share/fonts/X11/encodings/encodings.dir
        |   |   |-- fonts.cache-1
        |   |   `-- large
        |   |       |-- 
encodings.dir -> ../../../../../../share/fonts/X11/encodings/large/encodings.dir
        |   |       `-- fonts.cache-1
        |   |-- fonts.cache-1
        |   |-- misc
        |   |   |-- fonts.alias
        |   |   `-- fonts.cache-1
        |   `-- util
        |       `-- fonts.cache-1
        `-- twm -> /etc/X11/twm


any idea?

Regards,

Leo



A Dimecres 20 Setembre 2006 17:02, Neil Levine va escriure:
> Hi
>
> I am running FreeNX on a Debian unstable box:
>
> freenx  0.4.4+0.4.5-3
> nxagent 1.4.92+1.5.0-4
> nxlibs  1.4.92+1.5.0-4
>
> with the NoMachine nxclient (1.5.0-135-1).
>
> I authenticate to the remote server fine and I can see nx initialising
> on the server with the remote client appearing in the process list
> (xterm in this instance).
>
> However, nothing gets returned to the client display. Xterm sits in a
> select() until 30 seconds later the session times out ("No response
> received from the remote server.")
>
> I have seen the similar sypmtoms described here:
>
> http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ/Problem_Solving
>
> but nothing works/is relevant.
>
> This exact setup, with these exact versions _did_ work prior to an
> apt-get upgrade a week or so ago, so it is presumably something X server
> related, however, despite setting NX_LOG_LEVEL=7 no useful information
> is getting logged:
>
> NX> 706 Agent cookie: c23daaf3ff610a7d87af2cab004eda41
> NX> 704 Session cache: unix-application
> NX> 707 SSL tunneling: 1
> NX> 710 Session status: running
> NX> 1002 Commit
> NX> 1006 Session status: running
> NX> 105 bye
> Bye
> NX> 999 Bye
> NX> 1009 Session status: terminating
> NX> 1006 Session status: closed
> NX> 1001 Bye.
>
> .xsession-errors does not show any errors relating to the client either.
>
> Anywhere else I can look for potential clues?
>
> Neil
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>   http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>          Don't forget to check the NX Knowledge Base:
>                  http://www.nomachine.com/kb/
>
> ________________________________________________________________
>        FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>       https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________

-- 
--
Linux User 152692
PGP: 0xF944807E
Catalonia
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20060920/e54b67f4/attachment.sig>


More information about the FreeNX-kNX mailing list