neatx & NX 3.4.0: Alt Gr keeps stuck

[GoogleCodeExporter]

What steps will reproduce the problem?
1. enter a session (resume or create a new one, do not matter)
2. once press the Alt Gr 
3. key remains "pressed", no possibility to write normally from now on

What is the expected output? What do you see instead?
After once pressing Alt Gr normal key operation expected.

What version of the product are you using? On what operating system?
server: rev 59, nxclient 3.4.0-7, nxnode 3.4.0-11, RHEL 5.3
client: nxclient 3.4.0-7, fedora 12, german keyboard

Please provide any additional information below.

Original issue reported on code.google.com by erazo...@gmail.com on 12 May 2010 at 10:19

[GoogleCodeExporter]

Hi,

I found the source of the problem:

It comes from a change of the file Events.c in 
nx-X11/programs/Xserver/hw/nxagent, in
the available source code version (3.4.0-5) of nxagant.

The lines 790 to 803 are some of the additions which came into the code at the
version 3.4.0-4. 

There in the code you will find the following comment:
"FIXME: Don't enqueue the KeyRelease event if the key was
       not already pressed. This workaround avoids a fake
       KeyPress is enqueued by the XKEYBOARD extension.
       Another solution would be to let the events are
       enqueued and to remove the KeyPress afterwards."

I guess the matching entry in the changelog is the following: 
"Fixed TR09G02276. Now the agent does not receive unwanted characters
while interacting with the local window manager."

So obviously they wanted to cure something, but for me this broke anything... :(

By reverting their change I managed to get rid of my problem.
This means to change line 790 from "int sendKey = 0;" to "int sendKey = 1;".

I am very well aware that this patch is not really what one opts for, since a 
change
in neatx would have been much easier to handle, but I have no idea what to 
change in
neatx for making this work...

Greetings,
Theodor

Original comment by erazo...@gmail.com on 17 May 2010 at 12:13

[GoogleCodeExporter]

Hi again,

I just found out that it is possible to Download also the older versions of the
source files.
This makes it a little bit easier to handle that issue for users.
So what you need is just do download nxagent at the version 3.4.0-3.
(http://64.34.161.181/download/3.4.0/sources/nxagent-3.4.0-3.tar.gz)

But as this is the source you will need to compile on your own...

I have attached a way for doing this.

Greetings,
Theodor

Original comment by erazo...@gmail.com on 17 May 2010 at 1:04

Attachments:

• how2

[GoogleCodeExporter]

i have the same issue - with the most current Ubuntu 10.04 LTS packages

neatx-server 0.3.1+svn59-0~ppa1~lucid1
nxagent 1:3.4.0-3-0~ppa2~lucid1

Original comment by erich.fu...@gmail.com on 25 May 2010 at 12:57

[GoogleCodeExporter]

Same here:

- Ubuntu 10.04 
- x86_64
- neatx-server 0.3.1+svn59-0~ppa1~lucid1
- nxclient 3.4.0-7  

Original comment by kay.ra...@gmail.com on 14 Jun 2010 at 7:09

[GoogleCodeExporter]

I also had this problem, but when I was using nxclient connected to nxserver, 
NOT freenx.. Perhaps it's an issue with the nxclient?

Original comment by scott.be...@gmail.com on 18 Jun 2010 at 5:58

[GoogleCodeExporter]

Hi scott,

I do not quite understand how freenx plays into this game? Did you perhaps 
wanted to say neatx instead of freenx?

If this is the case, then yes I would that it is indeed possible to have the 
same issue with nxserver/nxagent 3.4.0 and older nxclients. But also in that 
case I would guess it is not because of the client but because of the agent, as 
the agent is the same for nxserver and neatx.
What nx versions did you use?

Original comment by erazo...@gmail.com on 19 Jun 2010 at 8:40

[GoogleCodeExporter]

Seems this issue has already been reported and fixed at NoMachine:
http://www.nomachine.com/tr/view.php?id=TR02H02327
It is however confusing that it says that it was fixed in nxagent-3.4.0-6.
I don't know how to check which NX Node version that are used in the nxclient.

Original comment by jens.lan...@gmail.com on 19 Jun 2010 at 10:15

[GoogleCodeExporter]

Hi Jens,

thanks a lot for this information!!
Yes so this bug seems to have been solved in nxnode source code version 3.4.0-6 
and binary version 3.4.0-13.
I will try it out!

Original comment by erazo...@gmail.com on 20 Jun 2010 at 2:19

[GoogleCodeExporter]

Ok so the error was indeed corrected by nx and current versions of nx binaries 
and source code is running as it should (at least for me).
Thanks again to Jens how spotted the new version.
So in principle this thread may be closed.

Original comment by erazo...@gmail.com on 21 Jun 2010 at 7:58

[GoogleCodeExporter]

    Hi erazortt,

Great that it works for you, but may I ask how/where you downloaded the 
binaries that worked? Because nxclient 3.4.0-7 is the latest client that I can 
find. If the correction was on the server side (NX node) it does not help much 
as long as neatx is used as server. And this is after all an issue on neatx.

Maybe neatx need a similar patch as the one made on the NX node sources to 
become compliant?

Original comment by jens.lan...@gmail.com on 22 Jun 2010 at 8:00

[GoogleCodeExporter]

Hi Jens,

the bug was on the server side. Indeed it is not in nxserver as this is what 
neatx replaces, but it is in nxnode. Nxnode is needed also for neatx and is the 
free part of the nx serverside. If you use linux or solaris you'll find it on 
the nx download page, it's in between nxclient and nxserver. (See 
http://www.nomachine.com/download.php)
If however you are using a distribution package of the nx serverside (as in 
ubuntu 10.04) I guess you cannot exchange just the node. In that case you 
should make a bug report at you distribution directly and ask for updates in 
the package, pointing to the bugreport of nx you posted earlier.
Alternatively you can compile the source code yourself, following the 
description I posted in this thread. However if you were not experienced in 
compiling I would not recommend this.

Greets

Original comment by erazo...@gmail.com on 23 Jun 2010 at 10:31