Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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
How reproducible:
always
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
Actual results:
keyboard setting does not change
Expected results:
keyboard keymap should change
Additional info:
Comment 4RHEL Program Management
2013-11-03 08:05:09 UTC
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'.
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 How reproducible: always 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 Actual results: keyboard setting does not change Expected results: keyboard keymap should change Additional info: