freenx-team team mailing list archive

[TheFinePrint <sjanten_@xxxxxxxxxxx>]

The problem with the evdev-solution is that it causes problems for those
users that may be on the physical machine.  E.g. when I log into my home
server over FreeNX the keyboard now works.  However if I log in locally
the keyboard is broken (same problem - except now in reverse).

Hence one must either change the keyboard layout every time one changes
login method, or one must choose which keyboard is more important;
remote or local.

There have been a number of updates, but the problem seems to persist.

-- 
Regression: Connecting to FreeNX breaks keyboard layout in Intrepid
https://bugs.launchpad.net/bugs/289918
You received this bug notification because you are a member of FreeNX
Team, which is the registrant for FreeNX Server.

Status in FreeNX open source NX Server: New
Status in “metacity” source package in Ubuntu: Confirmed

Bug description:
Details:
http://ubuntuforums.org/showthread.php?p=6043289&posted=1#post6043289

Story:
I have a Ubuntu 8.04.1 64bit server with FreeNX (used to be Debian Etch 4 with NomachineNX).  Then I have two 32bit clients, one with XP and one with Intrepid (used to be Hardy).  The Intrepid-client also has FreeNX (server) installed.

When it breaks the keymap is messed up to the point of not being usable in the NX-session.  Locally run programs are not affected.  Regular letters and numbers are not affected, but arrow keys and special keys such as pgup, pgdn, and delete are either not functioning or doing weird things (e.g. arrow up is remapped to screenshot).

The following works:
WinXP to Debian Nomachine
Hardy to Debian Nomachine
WinXP to Intrepid FreeNX
WinXP to Hardy FreeNX

The following is broken:
Intrepid to Hardy FreeNX
Intrepid to Intrepid FreeNX

Changing character-map on the FreeNX host does not help.  Keyboard works fine locally, and simultaneously with the NX-session (ie if I have a text editor on top the home key will work in the editor run locally, but nothing run remotely).