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:
Key mapping is working incorrectly in RDP connection to windows 8;

Version-Release number of selected component (if applicable):
hmm, maybe my russian keymap on my rhel is cause this bug.

How reproducible:


Steps to Reproduce:
1. Connect to windows 8 by rdp.
2. Open windows notepad and type some text.
3. Press left button

Actual results:
"4" symbol is typed 

Expected results:
cursor should be moved left

Additional info:
down arrow -> "2" is typed
up urrow -> "8"
left arrow -> "4"
delete button -> "."
escape -> i do not understand, but something is wrong

Hi,

thank you for this report. This bug has been fixed upstream in https://git.gnome.org/browse/vinagre/commit/?id=69acae5330c848cb7bf4094ebce34ccad798c6ca. The patch fixes the bug also in Red Hat Enterprise Linux 7. I'm proposing to fix this bug in upcoming minor release.

And when it will be fixed?

I've proposed the fix for 7.4 so if everything goes well then you will find it in 7.4 release of Red Hat Enterprise Linux.

And when 7.4 will be released? I think this is a critical bug: i can't work with vinagre.

I'm sorry, I can not comment on when the release will be available.

May be you have any useful answers for my questions? Do i need to wait for weeks, or months, or years?

You can approach our support and ask them about this.

Tested on vinagre-3.22.0-8.el7.x86_64
Problem did not appear.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2005