freenx-team team mailing list archive

[Alex <alex@xxxxxxxxxxxxxxx>]

I agree that this is a bug on the client, eg Ubuntu 8.10 - why should I
be forced to upgrade *all* my server systems (which don't run Ubuntu of
any flavour) just because I upgraded my client OS - note "OS" - not
client software.

Alex

On Tue, 2008-11-25 at 18:15 +0000, Martin Emrich wrote:
> Fixing or working-around this problem for every service does not really
> feel very satisfactory. I just upgraded NX Free on server and client,
> and after a quick test it seems to work. But I still sometimes (not
> always) have to do "setxkbmap -model evdev -layout de" on my laptop to
> make the keyboard work correctly.
> 
> Does anybody know what causes these problems? It is obviously the same
> keys (mostly cursor keys) for very many people with many different
> keyboards.
>

-- 
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).