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.
Bug 599306 - Some strange behaviors on key's appearance viewed by using vnc
Summary: Some strange behaviors on key's appearance viewed by using vnc
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: beta
: 6.1
Assignee: Gerd Hoffmann
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 580953
TreeView+ depends on / blocked
 
Reported: 2010-06-03 04:43 UTC by Mike Cao
Modified: 2013-01-09 22:40 UTC (History)
9 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.168.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 15:42:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1531 0 normal SHIPPED_LIVE Moderate: qemu-kvm security, bug fix, and enhancement update 2011-12-06 01:23:30 UTC

Description Mike Cao 2010-06-03 04:43:01 UTC 
Description of problem:

Version-Release number of selected component (if applicable):

rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.69.el6.x86_64

How reproducible:
always

strange behavior on press "Shift +characters"
Steps to Reproduce:
1. Start a windows 7 64bit Guest with -vnc and CapsLock is off.
2. right-click computer->Manage->Local Users and Groups
3. right-click user->new user
4. Make cursor focus on the password textbox.press on "Shift+m".
5. Release the 2 buttons at the same time ,notice that at the same time is a must.
6.repeat step 4 and step 5

Actual results:
After step 5,It prompts that "Caps Lock is On" but Caps Lock is off ,

Expected results:
It should NOT prompts anyting.

strange behavior on pressing "CapsLock +characters"
Steps to Reproduce:
1. Start a windows 7 64bit Guest with Caps Lock off 
2. open a notepad in the guest.
3. press "CapsLock+M"
4. Release the 2 buttons at the same time ,notice that at the same time is a must.
5. press "CapsLock+M"
6. Release the 2 buttons at the same time ,notice that at the same time is a must.
7. issue one character in notepad.

Actual results:
after step 7,the ouput character is uppercase letter,but CapsLock is off
Expected results:
the first ouput character should be lowercase letter.
Comment 2 RHEL Program Management 2010-06-07 15:58:11 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 4 RHEL Program Management 2010-07-15 14:02:04 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 5 RHEL Program Management 2010-10-07 19:18:19 UTC 
Thank you for your bug report. This issue was evaluated for inclusion
in the current release of Red Hat Enterprise Linux. Unfortunately, we
are unable to address this request in the current release. Because we
are in the final stage of Red Hat Enterprise Linux 6 development, only
significant, release-blocking issues involving serious regressions and
data corruption can be considered.

If you believe this issue meets the release blocking criteria as
defined and communicated to you by your Red Hat Support representative,
please ask your representative to file this issue as a blocker for the
current release. Otherwise, ask that it be evaluated for inclusion in
the next minor release of Red Hat Enterprise Linux.
Comment 8 Gerd Hoffmann 2011-02-15 08:40:07 UTC 
Backporting this one ...

http://git.qemu.org/qemu.git/commit/?id=9892088b52da05c3944e84982922fa984e048044

... will most likely fix this.

Don't think this qualifies as blocker though, so schedule for 6.2.
Comment 10 Gerd Hoffmann 2011-06-15 10:14:52 UTC 
https://brewweb.devel.redhat.com/taskinfo?taskID=3395634
Comment 14 Qunfang Zhang 2011-08-05 08:01:18 UTC 
Reproduce the 2 issues in the bug description on qemu-kvm-0.12.1.2-2.167.el6.

Retest on qemu-kvm-0.12.1.2-2.176.el6, the first issue 'strange behavior on press "Shift +characters" ' is gone.
But the second issue 'strange behavior on pressing "CapsLock +characters" '
still exists.
Comment 16 Gerd Hoffmann 2011-08-08 16:22:02 UTC 
There is no sane fix for the second issue.  CapsLock is different from the Shift and Control modifier.  It isn't designed to be hold down, instead a keypress toggles the CapsLock state.  There is no reliable way for qemu to figure the CapsLock state.  This isn't defined by the emulated hardware alone, but also by the guests keyboard driver.  Thus qemu uses some heuristics which are based on typical guest behavior, tricky corner cases like this one are impossible to get right as guests show slightly different behavior here.
Comment 17 Qunfang Zhang 2011-08-09 03:10:42 UTC 
Hi, Gerd
Thanks for the information, then I will change the status to VERIFIED as the first issue is fixed.
Comment 19 errata-xmlrpc 2011-12-06 15:42:36 UTC 
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.

http://rhn.redhat.com/errata/RHSA-2011-1531.html
Note You need to log in before you can comment on or make changes to this bug.