Bug 119296

Summary:	NX client does not work...
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Philippe Delval <phdelval>
Component:	Other	Assignee:	Stefan Dirsch <sndirsch>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None
Version:	RC 1
Target Milestone:	---
Hardware:	i686
OS:	SuSE Pro 9.2
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Philippe Delval 2005-09-28 20:14:39 UTC

I use to work with the NX client from NoMachine (v1.5.0-106) in Suse 9.2.
I've upgraded to Suse 10-RC1 and the NX client stop working. I've reinstalled it
and it give same error. 
So I do a fresh install of Suse 10, NoMachine NX client and kNX with the same
results. I can access the Free NX (v1.4.4?, last version) server from the
NoMachine client v1.5 in WindowsXP and Suse 9.2, so this is not an error with
the FreeNX in the server (Suse 9.2).
SSL encryption is enabled.
 
Here's the error:
 
NXPROXY - Version 1.5.0
 
Copyright (C) 2001, 2005 NoMachine.
See http://www.nomachine.com/ for more information.
 
Info: Proxy running in client mode with pid '5979'.
Warning: Connected to remote NXPROXY version 1.4.0 with local version 1.5.0.
Info: Synchronizing local and remote caches.
Info: Handshaking with remote proxy completed.
Info: Remote proxy doesn't support fake authentication.
Info: Forwarding the real X authorization cookie.
Info: Not using NX delta compression.
Info: Using lan link parameters 16384/8/0/0.
Info: Using pack method '16m-jpeg-9' with session 'unix-kde'.
Info: Not using ZLIB stream compression.
Info: Not using remote ZLIB stream compression.
Info: Not using persistent cache.
Info: Starting X protocol compression.
Warning: X connection failed with error 'Invalid MIT-MAGIC-COOKIE-1 key'.
Info: End of session requested by remote proxy.
Info: Shutting down the link and exiting.
 
Any idea?
Thanks in advance.

Comment 1 Stefan Dirsch 2005-09-29 09:45:38 UTC

Which packages have you installed exactly and in use on server and client?

  rpm -q NX FreeNX knx

Comment 2 Philippe Delval 2005-09-29 20:06:06 UTC

Server: Suse 9.2 + FreeNX-0.4.4? 
Server: rpm -q NX FreeNX knx:
NX-1.4.0-12.1
FreeNX-0.4.4-3

Client:
 - Originaly: Suse 9.2 + NX-1.5.0-17: OK
 - Later: Upgrade to Suse 10 OSS RC1: same error
        : + Reinstall NX-1.5.0-17: same error
 - Later: Fresh install pf Suse 10 OSS RC1 + kNX: same error
        : + install NX-1.5.0-17: same error
 - Later: Suse 9.2 in VMware 5.0 on Suse 10 OSS RC1 + NX-1.5.0-17: OK

Client: rpm -q NX FreeNX knx:
NX-1.5.0-17
FreeNX-0.4.4-4
knx-0.1-15

Comment 3 Stefan Dirsch 2005-09-29 20:21:30 UTC

You need the same NX version on both sides (server + client). Since SUSE 10.0 
comes with NX 1.5.0 you should use NX 1.5.0 also on the server. You need 
FreeNX 0.4.4 for NX 1.5.0. You find packages for SUSE 9.2/9.3 on our ftp 
server: 
 
--> ftp://ftp.suse.com/pub/suse/i386/supplementary/X/NX/

Comment 4 Philippe Delval 2005-09-29 22:46:15 UTC

Hi Stefan,

All is allright now. 
I didn't know these 'particularities' of the linux version of the NX Client and
I didn't see anything related to this in Google or the NoMachine web site.
Now, I know...

Thanks.

Philippe Delval.

Comment 5 Stefan Dirsch 2005-09-30 06:31:36 UTC

I'm not really happy with this situation. For now it's the best to use the 
latest NX, FreeNX and knx/nxclient on the server and the client to prevent 
such problems.

Comment 6 Philippe Delval 2005-09-30 07:34:06 UTC

Just make sure this is documented in the release notes or the packages for
now... And don't foget the readme on your ftp server! :-)
Thanks again for your efficiency resolving this problem.

Philippe.

Comment 7 Stefan Dirsch 2005-09-30 08:20:57 UTC

Good idea! I've added this information now to the README.SUSE of the packages
NX/FreeNX/knx (fixed for openSUSE 10.1 Alpha2) and updated the README on the ftp
server.

Comment 8 Philippe Delval 2005-09-30 10:56:01 UTC

Great! :-))