Hmm, I thought I got rid of this bug, but now it came back, in a more complex scenario:
I use the free version of NoMachine NX (www.nomachine.com) to connect from my home PC (current Intrepid, the one that had this bug a few weeks ago) to a PC at my university (current hardy). Inside the NX window, the keyboard exhibits the same behaviour as described here.
The "setxkbmap -model evdev" command does not help.
Hmm, I thought I got rid of this bug, but now it came back, in a more complex scenario:
I use the free version of NoMachine NX (www.nomachine.com) to connect from my home PC (current Intrepid, the one that had this bug a few weeks ago) to a PC at my university (current hardy). Inside the NX window, the keyboard exhibits the same behaviour as described here.
The "setxkbmap -model evdev" command does not help.