Description of problem:
This might actually be two seperate bugs, but one of them appears at random, and they seem to be pretty closely related.
Connecting to a guest with cursor in client mode can result in keyboard focus behaving somewhat strangely:
-- win key captured both by client and guest
-- (the random, barely reproducible) input redirected to guest even though virt-viewer doesn't appear to be focused (a different client side application should have the keyboard focus)
Version-Release number of selected component (if applicable):
Always (win key)
Steps to Reproduce:
1. Connect to a Windows 7 (or 8) guest (preferably with 2 monitors) with a windows 7 (or 8) client
2. Focus on a different application on clients side (don't have virt-viewer focused), move cursor out of the virt-viewer
3. alt+tab to virt-viewer (cursor still out of the window)
4. hit win key
Windows key gets grabbed both by client and guest.
Win key is captured just by guest
If you're lucky you'll notice the other bug as well (client applications won't be receiving input)
I can reproduce weird key grab issues too.
sent patch to ML
Win-key still gets grabbed by both client and guest when keyboard focus is in remote-viewer window, but mouse cursor is somewhere outside of it.
Everything works fine otherwise.
Is it a use case worth additional fixing?
(In reply to comment #3)
> Win-key still gets grabbed by both client and guest when keyboard focus is
> in remote-viewer window, but mouse cursor is somewhere outside of it.
> Everything works fine otherwise.
> Is it a use case worth additional fixing?
Yeah, received by both is a bug. I'll look into it.
This bug is partially fixed:
(1). remote-viewer window is in focus (cursor inside window): fixed.
before the fix windows-key is captured by both guest and client.
after the fix windows-key is captured only by guest, as expected.
(2). remote-viewer window is not in focus (cursor outside windows) not fixed.
windows-key is captured by both guest and client.
I'm going to mark this bug as fixed for case (1) above, and clone it for case (2).
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.