Red Hat Bugzilla – Bug 599306
Some strange behaviors on key's appearance viewed by using vnc
Last modified: 2013-01-09 17:40:08 EST
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.
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.
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. **
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.
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.
https://brewweb.devel.redhat.com/taskinfo?taskID=3395634
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.
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.
Hi, Gerd Thanks for the information, then I will change the status to VERIFIED as the first issue is fixed.
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