wk8 / neatx

Automatically exported from code.google.com/p/neatx
GNU General Public License v2.0
0 stars 2 forks source link

Removing FreeNX To Install Neatx #75

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. I installed Freenx, but it keeps crashing in middle of a session, so I'm 
trying to use Neatx instead.  The server is Debian Squeeze.
2.I installed Neatx according to these 
instructions:http://bladeswords.net/nx.html

But I use the latest files available:

wget http://64.34.161.181/download/3.5.0/sources/nxagent-3.5.0-7.tar.gz &
wget http://64.34.161.181/download/3.5.0/sources/nxcompext-3.5.0-1.tar.gz &
wget http://64.34.161.181/download/3.5.0/sources/nxcompsh-3.5.0-1.tar.gz &
wget http://64.34.161.181/download/3.5.0/sources/nxproxy-3.5.0-1.tar.gz &
wget http://64.34.161.181/download/3.5.0/sources/nx-X11-3.5.0-2.tar.gz &
wget http://64.34.161.181/download/3.5.0/sources/nxauth-3.5.0-1.tar.gz &
wget http://64.34.161.181/download/3.5.0/sources/nxcomp-3.5.0-2.tar.gz &
wget http://64.34.161.181/download/3.5.0/sources/nxcompshad-3.5.0-2.tar.gz

3.I inserted the new key into the client.
4.Some kind of connection almost starts, but it fails with this error:
NX> 500 Error: Session 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' has status 
'terminated', aborting

What is the expected output? What do you see instead?
I expect the window to open to my Debian desktop, but it fails with these 
details instead (server & username replaced with X's:

/***********START***********/
NX> 203 NXSSH running with pid: 8412
NX> 285 Enabling check on switch command
NX> 285 Enabling skip of SSH config files
NX> 285 Setting the preferred NX options
NX> 200 Connected to address: 192.168.2.152 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
Linux IRULEAN 2.6.32-5-686 #1 SMP Mon Oct 3 04:15:24 UTC 2011 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
HELLO NXSERVER - Version 3.3.0 - GPL
NX> 105 Hello nxclient - version 3.3.0
NX> 134 Accepted protocol: 3.3.0
NX> 105 Set SHELL_MODE: SHELL
NX> 105 Set AUTH_MODE: PASSWORD
NX> 105 Login
NX> 101 User: XXXXXXXX
NX> 102 Password: **********
Could not find ':' in DISPLAY: 
NX> 103 Welcome to: XXXXXXXXXX user: XXXXXXXX
NX> 105 Listsession --user="XXXXXXX" --status="suspended,running" 
--geometry="1280x1024x32+render" --type="unix-gnome"
NX> 127 Session list of user 'XXXXXXXX':
Display Type             Session ID                       Options  Depth Screen 
        Status      Session Name
------- ---------------- -------------------------------- -------- ----- 
-------------- ----------- ------------------------------

NX> 148 Server capacity: not reached for user: XXXXXXXX
NX> 105 Start session with: --link="lan" --backingstore="0" --encryption="1" 
--cache="32M" --images="64M" --defer="0" --shmem="0" --shpix="0" --strict="0" 
--composite="0" --media="0" --imagecompressionmethod="3" 
--imagecompressionlevel="-1" --render="0" --session="XXXXXXXX" 
--type="unix-gnome" --geometry="1274x996" --client="winnt" 
--keyboard="pc102/dvorak" --screeninfo="1274x996x32+render"
NX> 500 Error: Session '77D0CAC6DB4B9F506DF26A8809EBBB05' has status 
'terminated', aborting
NX> 999 Bye.
NX> 280 Exiting on signal: 15

/***********END*************/

What version of the product are you using? On what operating system?
The client is NoMachine NX Client for Windows 3.5.0.7

Please provide any additional information below.
I've seen this comment:
http://code.google.com/p/neatx/issues/detail?id=19#c10

And when I do this at the bash prompt:
which nxserver

I get this result:
/usr/bin/nxserver

I have seen this comment:
http://code.google.com/p/neatx/issues/detail?id=19#c11

And I KNOW I have used FreeNX here first, but I can't find any clues as to why 
this is wrong or what to do about it.

Original issue reported on code.google.com by ace.fr...@gmail.com on 2 Nov 2011 at 5:28