[FreeNX-kNX] Re: Connection error with ubuntu 10.04 & 10.10

[chris at ccburton.com]

Arnaud Fenioux <afenioux at gmail.com> wrote on 30/12/2010 15:19:12:

> On Wed, Dec 29, 2010 at 8:24 PM,  <chris at ccburton.com> wrote:
> [SNIP]
> > OK. Do you also always have:-
> > "Error: Aborting session with 'Could not open default font 'fixed''."
> Over ADSL
> no :
> InitOutput: Locale fr_FR.UTF-8 not supported by X
> InitOutput: cannot set locale modifiers.
> keyboard file created
> SessionPath not defined
> Session: Session started at 'Thu Dec 30 10:23:36 2010'.
> 
> over 3G, I also noticed that in .nx/<session>/errors :
> Loop: WARNING! Signals were not blocked in process with pid '5011'.
> Loop: PANIC! No shutdown of proxy link performed by remote proxy.

There is a bit of this sort of thing isn't there . . . . .


> > Try  connecting manually over the 3G and see what it says then
> > i.e ( depending on where nxnode is installed, I don't ubuntu)
> > ssh -X user at server -P port "/usr/bin/nxnode --agent :2000"
> >
> > You should get a blank nx screen with no crashes.
> 
> This is working over 3G :
> 
> ssh -X user at nxserver "/usr/lib/nx/nxnode --agent :2000"
> NX-:2000> 1000 NXNODE - Version 3.2.0-74-SVN OS (GPL, using backend: 
3.4.0)
> NX> 716 Starting NX Agent ...
> 
> NXAGENT - Version 3.4.0
> 
> Copyright (C) 2001, 2010 NoMachine.
> See http://www.nomachine.com/ for more information.
> 
> Info: Agent running with pid '31026'.
> Session: Starting session at 'Thu Dec 30 14:20:14 2010'.
> Info: Using alpha channel in render extension.
> Info: Not using local device configuration changes.
> InitOutput: Locale fr_FR.UTF-8 not supported by X
> InitOutput: cannot set locale modifiers.
> SessionPath not defined
> Session: Session started at 'Thu Dec 30 14:20:14 2010'.
> Info: Screen [0] resized to geometry [1592x900] fullscreen [0].
> Session: Terminating session at 'Thu Dec 30 14:20:18 2010'.
> Session: Session terminated at 'Thu Dec 30 14:20:18 2010'.
> FreeFontPath: FPE "/usr/share/fonts/X11/misc/" refcount is 2, should
> be 1; fixing.
> NX> 716 NX Agent exited with status: 0
> NX-:2000> 1001 Bye.
> 
> >
> > You can also run nxagent yourself
> >
> >  ssh -X user at server -P port
> >
> > /usr/bin/nxagent :2000
> > and see if you get any error messages.
> nop, also working!
> >
> > If you get the agent running, ssh again and in another session run
> >
> > export DISPLAY=:2000
> > startkde or gnome or whatever
> Working!

Right

Did you check out MTU over the 3G link.

There should be no difference whichever way it gets there, but 
a session which partially starts and then falls over with the server
complaining about losing the client is one (good) symptom of
path-MTU not working.

I guess you know how to check this out from reading your posts.

> 
> > You seem to have done a few re-installs, so if you can get it all
> > back to connecting via ADSL and then see if it still won't connect
> > from the same client to the same server via 3G we may be able
> > to pin it down.
> Well it's still not working with the nxclient under Ubuntu over 3G,
> but, after a test, it works under MS Windows over 3G (same server,
> same laptop, same signal power...)

Hmmmmm . . . well try MTU next is my advice, then.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20101230/d265386e/attachment.html>