| Summary: | Fix broken keymap for the default mac X11 server using gtk-vnc | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | derek |
| Component: | gtk-vnc | Assignee: | Daniel Berrangé <berrange> |
| Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2 | CC: | ask, berrange, dsulliva, rbinkhor, rvdwees, sputhenp, thogue, tpelka |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-08 14:41:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 745151 | ||
| Bug Blocks: | 782183, 1075802, 1172231, 1269194 | ||
|
Description
derek
2011-09-30 15:05:34 UTC
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative. Workaround: Shutdown VM(s) Open XML file for the related vm(s) in /etc/libvirt/qemu/ add "keymap='en-us'" without " " into the line that begins with <graphics /> (change en-us for other keymaps) restarted libvirtd to reload xml file 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. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
NB, while this problem is fixed upstream in 0.4.2, backporting it to the RHEL-6 version of gtk-vnc involves non-negligible risk, due to major code refactoring that took place upstream between the version RHEL-6 is shipping & the version containing the fix. As such the fix is not something that is desirable to backport to the RHEL-6 version of gtk-vnc. customer ran into this problem on the following windows 7 exceed for x windows server, and putty to create the ssh x11 tunnel this bz is tied more to to mac os, but not sure if the solution is generic in coverage for things like hummingbird exceed Maybe good to test common windows xservers. - hummingbird exceed - cygwin (definetly should test this one) Adding needinfo to ask if the upstream fix provides generic coverage for windows x11 servers. The upstream rewrite has provided a framework to allow us to easily support multiple different platforms. It has code to support Cygwin's XWin X11 server, but I've no information about exceed, so can't say whether that would work or not. It all depends on how the X server has decided to map the Windows keycodes, which is sadly different for almost every impl. Closing because per comment #8, the code changes involved in fixing this problem upstream are not reasonable to backport to RHEL-6 at this point in its lifecycle, nor is a rebase likely. |