Bug 1169286
Summary: | Incorrect shift key behaviour | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Tim Speetjens <tspeetje> |
Component: | mingw-virt-viewer | Assignee: | Pavel Grunt <pgrunt> |
Status: | CLOSED ERRATA | QA Contact: | SPICE QE bug list <spice-qe-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.5.0 | CC: | cfergeau, fidencio, gklein, lsurette, marcandre.lureau, pgrunt, rbalakri, sherold, tpelka, uril, yeylon, ykaul, ylavi |
Target Milestone: | ovirt-3.6.0-rc | ||
Target Release: | 3.6.0 | ||
Hardware: | x86_64 | ||
OS: | Windows | ||
URL: | https://bugs.freedesktop.org/show_bug.cgi?id=77259 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, the shift keys behaved incorrectly on Windows machines accessed with virt-viewer. When both shift keys were pressed at the same time and then released, Windows sent only one release key event, causing the SPICE client to think the other shift key is still pressed, and the guest to input capital letters. This has been fixed so GDK sends an extra release event so that both shift keys are released, and guest input is as expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-03-09 20:04:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Spice | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tim Speetjens
2014-12-01 09:14:02 UTC
Also, the same can be observed when doing the same, but exchanging left and right shift keys: 1. Press and hold right shift 2. Type a few letters: these are in caps 3. Press and hold left shift 4. Release right shift 5. Type a few letters: these are in caps 6. Release left shift 7. Type a few letters : these are also in caps, despite not holding down any shift key upstream bug 77259. imho, prio/severity could be low. What is the status of this issue? (In reply to Yaniv Dary from comment #3) > What is the status of this issue? We depend on a upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=751721 If it gets accepted there, the patch will be backported for the mingw-gtk package and included in the next build. 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://rhn.redhat.com/errata/RHEA-2016-0377.html |