Bug 1337230

Summary: Modifiers not sent to VM at times when mouse cursor is outside of remote-viewer window
Product: Red Hat Enterprise Linux 7 Reporter: David Jaša <djasa>
Component: spice-gtkAssignee: Default Assignee for SPICE Bugs <rh-spice-bugs>
Status: CLOSED INSUFFICIENT_DATA QA Contact: SPICE QE bug list <spice-qe-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: djasa, pgrunt, rbalakri, rduda, tpelka, vtosodec
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: 2016-06-10 08:27:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description David Jaša 2016-05-18 14:41:29 UTC
Description of problem:
Modifiers not sent to VM at times when mouse cursor is outside of remote-viewer window.

Version-Release number of selected component (if applicable):
spice-gtk3-0.31-2.el7.x86_64 (rebased and old - 7.2 - alike)
virt-viewer-2.0-7.el7.x86_64

How reproducible:
always (on my machine)

Steps to Reproduce:
1. open a terminal in a linux guest, type something
2. with mouse outside of client window, hit ctrl+W
3. move mouse into the window, hit ctrl+w again

Actual results:
2. "w" is printed as if ctrl was not pressed
3. whole word gets deleted

Expected results:
whole word gets deleted at 2. as well

Additional info:
upstream spice-gtk on Fedora doesn't suffer from this issue

Comment 1 Pavel Grunt 2016-05-19 09:43:04 UTC
(In reply to David Jaša from comment #0)
> 
> Additional info:
> upstream spice-gtk on Fedora doesn't suffer from this issue

spice-gtk in Fedora has the same version

Comment 2 Pavel Grunt 2016-05-23 08:55:38 UTC
Cannot reproduce using any client - I think something must be wrong in the env. Can you check if another app (eg gtk-vnc) has the same issue ?

Comment 3 Radek Duda 2016-05-25 14:58:49 UTC
Neither I can reproduce this bug.

Comment 4 David Jaša 2016-06-10 08:27:43 UTC
It seems that it's something unique to my system...