Back in the days of Gnome 2, I was happily using NX (NoMachine, FreeNX, neatx) for an extremely low-latency and usable connection to several Linux boxes. Everything worked like a dream.
Then, Gnome 3 came along, and it runs in fallback mode in NX. Keys started acting funny when I logged in, with down arrow becoming enter and lots of other strange stuff. I noticed that the keymaps were different from the NX session to the box I was connecting from, and after reading this post, I found that the following command (on any connect or resume) temporarily fixed the problem:
setxkbmap -model evdev -layout us
This is also confirmed on this bug report by NoMachine.
However, after my most recent upgrade to Gnome 3.6, this command doesn't fix things anymore. When I first start a session, keys do set of actions. If I run that command, they do a different set of actions, but still not the correct ones. There must be something distinctive about the way Gnome 3.6 is handling its keyboards versus Gnome 3.4/3.2, but I have no idea what it is. Perhaps some people can point out what changed with Gnome 3.6 so that I can use my system again.
Other posts about the issue, pre Gnome 3.6:
Before you flag this question as off-topic, please let me point out that NX is an extremely common tool for programmers, and Gnome 3 is the default display manager for many Linux distros. I feel that this question wouldn't get the right type of attention on AskUbuntu (I don't use Ubuntu) or SuperUser.
- Gnome 3.6 seems to have done some crazy things to the keyboard, which probably has something to do with it: http://anarsoul.blogspot.com/2012/10/gnome-36-and-keyboard-layout.html