[FreeNX-kNX] Problem connecting to FreeNX 0.6.0 (amd64)
Zach Tibbitts
zach at collegegeek.org
Wed Apr 25 19:32:35 UTC 2007
Now I'm getting a font problem:
zach at cervantes:~/.nx$ cat
C-cervantes-1000-958F9D2DE4CC1FC3FB7D38CB47ACE0D2/session
*snip*
Warning: Unable to retrieve the supported pack methods.
Info: Using shared memory parameters 1/1/0/0.
Warning: Render not available on the remote display.
XpmError: XpmColorFailed
nxagentInitAtomMap: WARNING XInternAtoms failed.
Info: No window manager has been detected.
nxagentOpenScreen: Forcing fullscreen mode with no window manager running,
Info: Using local device configuration changes.
nxagentRealizeFont: WARNING! Can't load font 'fixed' with X connection
not available.
Fatal server error:
could not open default font 'fixed'
Zach Tibbitts wrote:
> Here's the session file:
>
> zach at cervantes:~/.nx/C-cervantes-1000-7E47E3214EC11DC47434BC925651EDBB$
> cat session
>
> NXAGENT - Version 2.1.0
>
> Copyright (C) 2001, 2006 NoMachine.
> See http://www.nomachine.com/ for more information.
>
> Info: Agent running with pid '11073'.
> Session: Starting session at 'Wed Apr 25 13:31:21 2007'.
> Info: Proxy running in server mode with pid '11073'.
> Info: Waiting for connection from '127.0.0.1' on port '5000'.
> Info: Accepted connection from '127.0.0.1' with port '43897'.
> Info: Connection with remote proxy established.
> Info: Synchronizing local and remote caches.
> Info: Handshaking with remote proxy completed.
> Info: Using adsl link parameters 512/24/1/1.
> Info: Using agent parameters 5000/50/1/0.
> Info: Using cache parameters 4/4194304/8192KB/8192KB.
> Info: Using image streaming parameters 50/128/1024KB/2048/256.
> Info: Using pack method 'no-pack' with session 'unix-application'.
> Info: Using ZLIB data compression 3/3/32.
> Info: Using ZLIB stream compression 6/6.
> Info: No suitable cache file found.
> Info: Established X client connection.
> Info: Using shared memory parameters 1/1/1/2048K.
> Info: Detected window manager running.
> Info: Not using local device configuration changes.
> Info: Using alpha channel in render extension.
> XIO: fatal IO error 104 (Connection reset by peer) on X server
> "unix:1000.0"
> after 0 requests (0 known processed) with 0 events remaining.
> Agent pid 11126
> xscreensaver: Can't open display: unix:1000
> xscreensaver: running as zach/zach (1000/1000)
>
> xscreensaver: Errors at startup are usually authorization problems.
> But you're not logging in as root (good!) so something
> else must be wrong. Did you read the manual and the FAQ?
>
> http://www.jwz.org/xscreensaver/faq.html
> http://www.jwz.org/xscreensaver/man.html
>
>
> (xfce4-session:11134): Gtk-WARNING **: cannot open display:
> Agent pid 11126 killed
>
> It looks like some permissions are set wrong, and I can't start X as my
> user. If you know
> how to fix that, I'd appreciate it, I'm going to do some googling.
>
> Alastair Johnson wrote:
>
>> It looks like your X session is terminating immediately. Because the X session
>> is finished NX terminates the connection.
>>
>> To find out why you need to enable logging and disable cleanup of session
>> logs. Do this by setting the following in /etc/nxserver/node.conf
>> NX_LOG_LEVEL=3
>> SESSION_LOG_CLEAN=0
>> You could set the log level up to 7 if you like.
>>
>> After a failed session check in ~/.nx/[big ling session ident here]/session
>> and errors to see what happened.
>>
>> On Wednesday 25 April 2007 16:21, Zach Tibbitts wrote:
>>
>>
>>> I've just built and installed FreeNX 0.6.0 using Fabian's patch, and
>>> everything seems to have installed properly. However, when I try to
>>> connect to the sever, I have problems. I'm using the official nomachine
>>> 2.1.0 client. Here's the output, the configuration is a custom unix
>>> desktop that runs startxfce4.
>>>
>>> NXPROXY - Version 2.1.0
>>>
>>> Copyright (C) 2001, 2006 NoMachine.
>>> See http://www.nomachine.com/ for more information.
>>>
>>> Info: Proxy running in client mode with pid '8485'.
>>> Session: Starting session at 'Wed Apr 25 11:17:40 2007'.
>>> Info: Synchronizing local and remote caches.
>>> Info: Handshaking with remote proxy completed.
>>> Info: Using adsl link parameters 512/24/1/1.
>>> Info: Using cache parameters 4/4194304/8192KB/8192KB.
>>> Info: Using image streaming parameters 50/128/1024KB/2048/256.
>>> Info: Using pack method 'no-pack' with session 'unix-application'.
>>> Info: Using ZLIB data compression 3/3/0.
>>> Info: Using ZLIB stream compression 6/6.
>>> Info: No suitable cache file found.
>>> Info: Listening for font server connections on port '11000'.
>>> Session: Session started at 'Wed Apr 25 11:17:40 2007'.
>>> Info: Established X server connection.
>>> Info: Using shared memory parameters 1/2048K.
>>> Session: Terminating session at 'Wed Apr 25 11:18:42 2007'.
>>> Info: End of NX transport requested by signal '15'.
>>> ________________________________________________________________
>>> 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
>>> ________________________________________________________________
>>>
>>>
>> ________________________________________________________________
>> 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
>> ________________________________________________________________
>>
>>
>
> ________________________________________________________________
> 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
> ________________________________________________________________
>
More information about the FreeNX-kNX
mailing list