Cursor Keys not working with NXClient

Bug #361903 reported by Reinhard Berger
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

Under jaunty the curor keys are not working anymore when a connection with "NXClient" has been etablished.

All other keys incl. F and ALT Keys are working.

Revision history for this message
Misoldgit (simonrhart) wrote :

I'm running Jaunty on a Dell Vostro 1510 laptop and use a VPN to work remotely on my Hardy workstation at work. I've run Nxclient tonight for the first time and the cursor keypad doesnt work. I've tried using it in xterm and in GVIM. The keyboard keys for up/down (j/k etc) etc do work in GVIM tho.

Revision history for this message
Reinhard Berger (geist1) wrote :

I've found the solution by the Nomachine website.

The reason why this happen is the newer XServer 1.6

When you use 2 diffrent NX Systems (a older one with V 2.) on e.g. ubuntu 8.04 and a newer one V3.x - or even a V2 one on a newer XServer 1.6 (e.g. ubuntu 9.04) then this cursor keys are mapped incorrectly to the V2 NX Server.

The solution is either - if possible - update the V2 Server to a V3 Version , or if not possible add on your NX CLIENT Side the following lines into the /etc/x11/ xorg.conf file :

Section "ServerFlags"
 Option "AutoAddDevices" "false"

Note : Adding this will disable local country keyboard support, the keyboard is then set to US/English

To enable locale keyboard support again, you must write the following :

Section "InputDevice"
 Identifier "Keyboard0"
 Driver "kbd"
 Option "XkbLayout" "de"

For Example this will enable german = "de" keyboard support.

After adding this a restart of the X-Server is required.

 For more info see : http://www.nomachine.com/tr/view.php?id=TR11F02131

Revision history for this message
Misoldgit (simonrhart) wrote :

Thanks for the info but I'm not sure it works.

I have the nxserver running on Hardy and it's a version 3.2.0-14 and the nxclient running on Jaunty and that is 3.3.0-6 but the cursor problem remains. I'm getting the versions from the about page in the nomachine configuration options - I hope that is the correct place.

I havent tried the xorg.conf change but I will

Revision history for this message
Misoldgit (simonrhart) wrote :

I have made the suggested changes to my xorg.conf and I'm pleased to report the cursor keys now work!
My changes to xorg.conf for a uk keyboard are:

# All following added to fix no cursor keys in NXClient
Section "ServerFlags"
 Option "AutoAddDevices" "false"
EndSection

Section "InputDevice"
 Identifier "Keyboard0"
 Driver "kbd"
 Option "XkbLayout" "gb"
EndSection

Many thanks

Revision history for this message
Misoldgit (simonrhart) wrote :

One note..

The above change kills my mouse scroll via the trackpad on my laptop. I'm sure this is resolvable but I havent yet.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid or Maverick packages ?
Tanks in advance.

Changed in ubuntu:
status: New → Incomplete
Changed in ubuntu:
status: Incomplete → Fix Released
Revision history for this message
Murz (murznn) wrote :

Have the same problem on Lucid as nxclient and Debian Squeeze as nxserver.

Revision history for this message
Murz (murznn) wrote :

After adding strings:

# All following added to fix no cursor keys in NXClient
Section "ServerFlags"
 Option "AutoAddDevices" "false"
EndSection

Section "InputDevice"
 Identifier "Keyboard0"
 Driver "kbd"
 Option "XkbLayout" "gb"
EndSection

I lost control computer by keyboard :(

Changed in ubuntu:
status: Fix Released → New
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Sorry for the accident but i've recived a mail from one of the subscribers that tells that the problem was fixed, then i mark it so, without controlling that it was in launchpad too.
Excuse me again.
can you run a live Cd and delete the added strings ?

Revision history for this message
Reinhard Berger (geist1) wrote :

The get this thing working, you must have the same version of NXCleint and NXServer running on the machines.

If not both versions are 3.4.x it will not work.

Example : If you have Version less then 3.4 on server side and client version 3.4.x then it does not work.

Both Server and Client need to be have the same version, if you only change server or client it doesnt work too.

Tested with hardy 8.04 with nxserver 3.4.0-12 and lucid 10.04 with nxclient 3.4.0-7.

Also i think if both system uses same X-Server Version the bug should not appear even on older nxcleint/nxserver - dont't know for sure just think so.

The Bug is fixed since NoMachine released newer versions of nxcleint/nxserver.

Either this is still a bug in X-Server and NoMachine works around of this wiith thier new versions, or the NXServer program itself has had a bug with X-Server 1.6 - hard to tell where the problem is.

But since it is working now with newer versions of NXServer/NXCleint this bug is gone and this is the main thing , doesnt matter how it has been fixed.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and Ubuntu the following pages should be informative:

1. http://www.ubuntu.com/project/about-ubuntu/components - information about Ubuntu repositories
2. https://help.ubuntu.com/community/Repositories - information regarding managing repositories

Changed in ubuntu:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.