Red Hat Bugzilla – Bug 1024390
tigervnc resets the keyboard mapping
Last modified: 2015-06-15 19:53:07 EDT
Description of problem:
keyboard mapping resets to default keyboard in vncserver
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 6.4
Steps to Reproduce:
1. Install tiger vncserver and configure for user test on server A.
2. Change keyboard keycode by xmodmap
xmodmap -e "keycode 29=z"
3. Now from other system client B connect to server A via vncviewer
keyboard setting does not change
keyboard keymap should change
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Please provide more details what behaviour is expected and the exact setup and sequence of commands used on the various hosts/clients. I tried this on an up-to-date RHEL 6.6 and as far as I can tell this is a feature, not a bug.
tigervnc tries to map the keysym into a keycode to provide the right behaviour on the clients. This behaviour ensures that a client connecting with a qwerty keyboard layout on the host can use it as-is, and a client connecting with an azerty layout likewise. No reconfiguration of keyboards is thus necessary.
This is a feature, to achieve the outcome expected in comment #1 you'd have to run the xmodmap on the machine the host vncviewer is running on, so that vncviewer sends 'z', not 'y'.