[FreeNX-kNX] blank screen issue

Terje Andersen terander at guard.zapto.org
Thu Jul 24 19:42:09 UTC 2008


On Thursday 24 July 2008 11:15:07 Alastair Johnson wrote:
> Reply inline below...
>
> Aidan Marks wrote:
> > Hi
> >
> > gentoo hardened server with nx-3.2.0-r3, nxserver-freenx-0.7.2-r2,
> > xorg-server-1.4.2, kde 4.0.5
> >
> > gentoo laptop client, nxclient-3.2.0.13
>
> Desktop profile with xorg-server-1.3.0.0-r6 here, but not too dissimilar
>
> > client sees a blank screen after the !m. this used to work fine, can't
> > pinpoint the regression.
> >

Blank screen has meant for me that there are some fonts either missing, or not 
found. You can add the path to them, if that's the case, with the X Agent 
extra params in the node.conf file.

<snip>

> > session log:
> >
> > NXAGENT - Version 3.2.0
> >
> > Copyright (C) 2001, 2007 NoMachine.
> > See http://www.nomachine.com/ for more information.
> >
> > Info: Agent running with pid '4413'.
> > Session: Starting session at 'Fri Jul 11 09:24:06 2008'.
> > Info: Proxy running in server mode with pid '4413'.
> > Info: Waiting for connection from '127.0.0.1' on port '5000'.
> > Info: Accepted connection from '127.0.0.1'.
> > Info: Connection with remote proxy completed.
> > Info: Using LAN link parameters 1536/24/1/0.
> > Info: Using agent parameters 5000/0/50/0/0.
> > Info: Using pack method 'adaptive-9' with session 'unix-kde'.
> > Info: Not using NX delta compression.
> > Info: Not using ZLIB data compression.
> > Info: Not using ZLIB stream compression.
> > Info: Not using a persistent cache.
> > Info: Listening to X11 connections on display ':1000'.
> > Info: Established X client connection.
> > Info: Using shared memory parameters 1/1/1/2048K.
> > Info: Using alpha channel in render extension.
> > Info: Not using local device configuration changes.
> > Session: Session started at 'Fri Jul 11 09:24:09 2008'.
> > Info: Screen [0] resized to geometry [1016x706].
> > Session: Terminating session at 'Fri Jul 11 09:26:05 2008'.
>
> X just terminated. Check the session errors file. If there's nothing
> there then it thinks your X session terminated cleanly. It may be worth
> setting the log level to maximum (7?) as it might log something useful.
>

You could also, in addition to the /var/log/nxserver.log file (after 
increasing the log level as per instructions from Alastair(, look 
in "<homedir of the user>/.nx/F-<session-id>/errors" file for more info.

Regards,
Terje



More information about the FreeNX-kNX mailing list