[FreeNX-kNX] FreeNX 0.4.1 "LinuxTag Edition" Release Announcement

[Christian Leber]

On Wed, Jun 29, 2005 at 12:01:08AM +0200, Fabian Franz wrote:

>   * Added suspend/resume support for 1.5.0 OSS components.

great work!

>   * Fixed display of suspended sessions in nxserver --list.

>  --> http://www.nomachine.com/sources/development/
>      (read http://www.nomachine.com/news_read.php?idnews=156), or

So I installed the stuff (1.5) from here as described in the INSTALL file.

And used as client a windows 2000 system with nxclient 1.4.0-92 and it
worked exactly _one_ time with my normal username, so PAM did also work.

But I was not able to close the nxclient again, so I killed it and
from this point on, it doesn't work anymore, it fails allways with
"sessioon startup failed".
Of course I restarted the client system, did nxserver --stop/start etc.
pp.

So I added a user "nxtest" and it doesn't the same way, i also used
--adduser, but that didn't help either, it fails the same way, the error
log is:

NX> 203 NXSSH running with pid: 1296
NX> 285 Enabling skip of SSH config files
NX> 200 Connected to address: 192.168.3.3 on port: 22
NX> 202 Authenticating user: nx
NX> 208 Using auth method: publickey
HELLO NXSERVER - Version 1.4.0-04-CVS OS (GPL)
NX> 105 hello NXCLIENT - Version 1.4.0
NX> 134 Accepted protocol: 1.4.0
NX> 105 SET SHELL_MODE SHELL
NX> 105 SET AUTH_MODE PASSWORD
NX> 105 login
NX> 101 User: nxtest
NX> 102 Password:
NX> 103 Welcome to: core user: nxtest
NX> 105 listsession --user="nxtest" --status="Suspended","Running" --geometry="1600x1200x16+render" --type="unix-kde"
NX> 127 Sessions list of user 'nxtest' for reconnect:

Display Type             Session ID                       Options  Depth Screen         Status      Session Name
 ------- ---------------- -------------------------------- -------- ----- -------------- ----------- ------------------------------


NX> 148 Server capacity: not reached for user: nxtest
NX> 105 startsession --session="test2" --type="unix-kde" --cache="8M" --images="32M" --cookie="1f2cb308e9d92c606d92ee4114b9afd0" --link="adsl^A" --kbtype="pc102/de" --nodelay="1" --backingstore="never" --geometry="fullscreen" --media="0" --agent_server="" --agent_user="" --agent_password=""  --screeninfo="1537x1200x16+render"

NX> 1000 NXNODE - Version 1.4.0-04-CVS OS (GPL)
NX> 700 Session id: core-1008-2FBAFA869B9C4997F654739F18C2C43C
NX> 705 Session display: 1008
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: 09bc2cdbc524c335214b12979ba7ef74
NX> 702 Proxy IP: 192.168.3.153
NX> 706 Agent cookie: 1f2cb308e9d92c606d92ee4114b9afd0
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 0
NX> 105 NX> 504 Session startup failed.
NX> 1004 Error: nxagent failed to start. Session timed out.
NX> 1001 Bye.


When this happens there are a few processes started by nxserver:
core:/usr/NX# ps aux|grep nxtest
nxtest   18222  0.0  0.0   2668  1376 ?        S    15:56   0:00 /bin/bash /usr/NX/bin/nxnode --startsession
nxtest   18236  0.3  0.0   2412  1100 ?        S    15:56   0:00 /bin/sh /usr/bin/startkde
nxtest   18257  0.0  0.3  12484  4832 ?        S    15:56   0:00 dcopserver
nxtest   18419  0.0  0.3  21592  5112 ?        R    15:56   0:00 kpersonalizer --r --before-session


What could be my problem?


Christian Leber

-- 
http://www.nosoftwarepatents.com