[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freenx-knx
Subject:    Re: [FreeNX-kNX] FreeNX+QGIS: reproducible connection shut downs
From:       Terje Andersen <terander () guard ! zapto ! org>
Date:       2008-03-13 21:41:08
Message-ID: 1205444468.6161.9.camel () ante-laptop ! mailworld ! lan
[Download RAW message or body]

On Thu, 2008-03-13 at 18:11 +0100, Maciej Sieczka wrote:
> Murray Trainer pisze:
> > On Tue, 2008-03-11 at 08:37 +0100, Maciej Sieczka wrote:
> 
> >> Can you point me to the report for the NoMachine you mentioned in your 
> >> previous email?
> 
> > http://www.nomachine.com/tr/view.php?id=TR12E01973
> 
> Thanks.
> 
> They say the issue has been just fixed [1], on 2008-03-12. Any chances 
> the fix will be included in FreeNX 0.7.2? That'd be great...

According to the information from NoMachine [1], it is a protocol
fix which will be released in the 3.2 version of nxlibs. nxlibs isn't a
part of FreeNX itself, though FreeNX depends on nxlibs.

This change will change the protocol and this needs to be implemented in
FreeNX (and potentially QtNX) though.

[1]From NoMachine:
"This fix can't be released under 3.1.0. It would require a change in the
protocol breaking compatibility with previous versions. Node and Client
need to be released under 3.2.0 in order to get the problem fixed.
Version 3.2.0 will include the protocol negotiation in order to use old
protocol when connected to an older NX proxy."

	/Terje

________________________________________________________________
     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@kde.org
      https://mail.kde.org/mailman/listinfo/freenx-knx
________________________________________________________________
[prev in list] [next in list] [prev in thread] [next in thread]