[FreeNX-kNX] NX disappears after starting

[mashtin.bakir at gmail.com]

That did it. While both good and bad hosts had
xorg-x11-fonts-misc installed and they both had the
aforementioned directory, the failing hosts were missing
fonts.dir (but had fonts.alias)


Thanks!!!


On Fri, May 3, 2013 at 3:13 PM, Chris <chris at ccburton.com> wrote:

>
> freenx-knx-bounces at kde.org wrote on 03/05/2013 19:54:14:
>
> [SNIP]
>
> > NXAGENT - Version 3.3.0
> >
> > Copyright (C) 2001, 2007 NoMachine.
> > See http://www.nomachine.com/ for more information.
> >
> > Info: Agent running with pid '4598'.
> > Session: Starting session at 'Fri May  3 14:40:46 2013'.
> > Info: Proxy running in server mode with pid '4598'.
> > Info: Waiting for connection from '127.0.0.1' on port '6001'.
> > Info: Accepted connection from '127.0.0.1'.
> > Warning: Connected to remote version 3.5.0 with local version 3.3.0.
> > Warning: Consider checking http://www.nomachine.com/ for updates.
> > 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-desktop'.
> > Info: Using product 'LFE/None/LFEN/None'.
> > 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 ':2001'.
> > Info: Established X client connection.
> > Info: Using shared memory parameters 1/1/0/0K.
> > Info: Using alpha channel in render extension.
> > Info: Using local device configuration changes.
> > Error: Aborting session with 'Could not open default font 'fixed''.
> > Session: Aborting session at 'Fri May  3 14:40:50 2013'.
> > Session: Session aborted at 'Fri May  3 14:40:50 2013'.
> > Warning: Signals were not blocked in process with pid '4598'.
> > Info: Watchdog running with pid '4644'.
> > Info: Waiting the watchdog process to complete.
> > xrdb: Connection refused
> > xrdb: Can't open display ':2001'
> > xterm Xt error: Can't open display: :2001
> >
> >
> >
> >
>
> > Like I said, I can start up an alternate Xserver on the windows
> > host, ssh into the problem, set DISPLAY back to the windows
> > host and start an X application (eg xterm).
>
> We can all do that,
> because
> ssh does X forwarding
> so
> if you point your DISPLAY at it
> xterm hits your session sshd child
> and
> gets forwarded to your client Xserver
>
>
> >
> > Are there some nx commands I could run that
> > way to pin-point the problem?
>
> No. It's not FreeNX anyway. It's an nxagent issue.
>
>
> You could read your log tho' and look for the error message.
>
> Do you have
>         xorg-x11-fonts-misc
> installed ??
>
> Do you have such a directory as :-
>         /usr/share/X11/fonts/misc/fonts.dir
> ??
>
>
> > Thanks
> >
>
>
> ________________________________________________________________
>      Were you helped on this list with your FreeNX problem?
>     Then please write up the solution in the FreeNX Wiki/FAQ:
>
> http://openfacts2.berlios.de/wikien/index.php/BerliosProject: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
> ________________________________________________________________
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20130503/9cd709fb/attachment.html>