[FreeNX-kNX] again problems ... X not starting

Adrian Coman adi.coman at gmail.com
Mon May 23 07:34:41 UTC 2005


I have freenx-0.4.0-0.fdr.1.noarch.rpm and nx-1.4.0-0.fdr.4.i386.rpm 
installed on a CentOS4 and when I'm trying to start a session (locally 
or remote - the same problem) the authentification goes OK but the X 
window never starts. The nxlog looks like:

[root at adi nxserver]# tail -f /var/log/nxserver.log
-- NX SERVER START: -c /usr/bin/nxserver
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: adi
NX> 102 Password:
NX> 103 Welcome to: adi user: adi
NX> 105 listsession --user="adi" --status="Suspended","Running" 
--geometry="1280x1024x16+render" --type="unix-kde"
NX> 127 Sessions list of user 'adi' for reconnect:

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


NX> 148 Server capacity: not reached for user: adi
NX> 105 startsession --session="adi at homeKNX" --type="unix-kde" 
--cache="8M" --images="32M" --cookie="b37a0de5f50c13f865aecfff86592145" 
--link="modem" --kbtype="pc102/ro" --nodelay="1" 
--backingstore="when_requested" --geometry="1280x1024+0+0" --media="0" 
--agent_server="" --agent_user="" --agent_password=""  
--screeninfo="1280x1024x16+render"

NX> 1000 NXNODE - Version 1.4.0-04-CVS OS (GPL)
NX> 700 Session id: adi-1000-273E4FC5682EBDF163169B2880E1268B
NX> 705 Session display: 1000
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: aa580170b77fb0cda888af182ff804c4
NX> 702 Proxy IP: 212.93.145.144
NX> 706 Agent cookie: b37a0de5f50c13f865aecfff86592145
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 0
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 bye
Bye
NX> 999 Bye
NX> 1001 Bye.


What could be the problem?

Thanks,
Adrian



More information about the FreeNX-kNX mailing list