GNOME Bugzilla – Bug 157685
Caps lock confusion
Last modified: 2005-05-20 16:26:46 UTC
This bug has been reported here: https://bugzilla.ubuntu.com/2785 "There is some confusing behaviour on vino. Firstly, caps lock doesn't seem to enable capitals in an xterm when used remotely (however, it does turn on the caps lock light on the base desktop machine keyboard). Secondly, the state of caps/no caps can get confused between ubuntu and the host client. Follow these steps: 1) Install Tight VNC Viewer 1.2.9 (win 2k in my case) 2) Connect to ubuntu shared desktop, open an xterm 3) In the xterm, type some text, then hit caps lock key (any text typed now isn't capitalised - first problem) 4) Switch focus on the host to another window other than the vnc client, hit caps lock 5) Switch back to ubuntu shared desktop and type more text in the xterm (any text typed now is in capitals, not what is expected). This is incredibly confusing, especially for users who don't have the wont to mess around until things work as expected."
Should be fixed on HEAD and gnome-2-10 now: 2005-05-20 Mark McLoughlin <mark@skynet.ie> Fix some keyboard handling bugs: 1) Shift key not working for some charactes (bug #155900) 2) Caps lock not working (bug #157685) 3) Key repeat issue: https://bugzilla.redhat.com/134451 * server/vino-input.c: (vino_input_initialize_keycodes): if the keysym is defined multiple times in the mapping, choose the first one. (vino_input_handle_key_event): ignore Caps Lock altogether and send a key press/release pair to the Xserver for each press, rather than waiting for the release. The Xserver on the client can handle key repeating.