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 1275231 - Fullscreen multi monitor setup: Alt-Tab processed by client
Summary: Fullscreen multi monitor setup: Alt-Tab processed by client
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spice-gtk
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 7.2
Assignee: Victor Toso
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks: 1322914 1330652
TreeView+ depends on / blocked
 
Reported: 2015-10-26 10:17 UTC by Andrei Stepanov
Modified: 2016-11-04 01:12 UTC (History)
8 users (show)

Fixed In Version: spice-gtk-0.26-6.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1322914 1330652 (view as bug list)
Environment:
Last Closed: 2016-11-04 01:12:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Example for Alt-Tab (1.25 MB, image/jpeg)
2015-10-26 10:17 UTC, Andrei Stepanov 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2229 0 normal SHIPPED_LIVE virt-viewer, libgovirt, spice-gtk, and usbredir bug fix and enhancement update 2016-11-03 13:26:58 UTC

Description Andrei Stepanov 2015-10-26 10:17:15 UTC 
Created attachment 1086440 [details]
Example for Alt-Tab

There is quite unpleasant behavior for fullscreen multi monitor setup.
Particularly, Alt-Tab event goes to client's windowmanager.
This can really confuse a user.

Bug takes place in setup with 2 (or more) real monitors.

Steps to reproduce:

1. Have a client with real two monitors.
2. Activate in virt-viewer additional monitors == real monitors.
3. Connect to VM with virt-viewer --full-screen

Each virtual display should be positioned on real monitor.

4. Move mouse pointer to one of displays. Open a window.
5. Move mouse pointer to other display. Do not click mouse.
6. Press: Alt-Tab.

Alt-Tab will be processed by client's WM.

There is work around: always click with mouse as you move to another display.
Nonetheless I find this behavior very annoying.

See attached screenshot.
Comment 2 Fabiano Fidêncio 2015-10-26 10:41:05 UTC 
Testing here (using rhel-7.2/f22 client connecting to rhel-7.2/f22 guest) and the only way to have the Alt+Tab handled by the client's Window Manager is when pressing Alt+Tab with the top menu (that contains the "Leave Fullscreen" button) focused.
Comment 3 Andrei Stepanov 2015-10-26 10:51:15 UTC 
My setup has client 7.2
It doesn't depend on guest type.
It is reproducible without invocation the menu at the top.
Comment 4 Fabiano Fidêncio 2015-10-26 23:33:16 UTC 
Hmm. I take the comment 2 back, I _can_ reproduce it here and it's quite interesting :-)
Every time you move the mouse from one display to another spice-gtk ungrabs the mouse and any keyboard event goes to the client's DE.

I can easily reproduce it with just one remote-viewer window, windowed mode, vertically maximized (Alt + {right,left}, when using GNOME). Just move the mouse to the "guest's area" without do any click and then press Alt + Tab, same behavior.

Andrei, does it happen with 6.7/rhevm clients as well? Can you check if it's a regression?

As I said before, I am able to reproduce it and I am using upstream spice-gtk/virt-viewer.
Comment 5 Fabiano Fidêncio 2015-10-27 16:48:53 UTC 
Proposed a patch upstream for spice-gtk:
http://lists.freedesktop.org/archives/spice-devel/2015-October/022793.html
Comment 6 Pavel Grunt 2015-11-02 17:38:43 UTC 
(In reply to Fabiano Fidêncio from comment #5)
> Proposed a patch upstream for spice-gtk:
> http://lists.freedesktop.org/archives/spice-devel/2015-October/022793.html

Currently the keyboard grab (redirection of key events) is related to a SpiceDisplay (virt-viewer's window), we can make it related to the application (session). IE if mouse is over any window of virt-viewer and any virt-viewer's window has the focus, then key events should be redirected.
Comment 7 Uri Lublin 2015-11-05 08:52:38 UTC 
To reproduce at step 4 (from comment 0) I
4. Move mouse pointer to one of displays and left-click in it.
Comment 8 Pavel Grunt 2015-12-21 18:05:32 UTC 
Fixed upstream:
http://cgit.freedesktop.org/spice/spice-gtk/commit/?id=143ebfdf275a7743ca4332dc526991f8bd95124a
Comment 10 Andrei Stepanov 2016-03-30 16:49:26 UTC 
I cannot reproduce the bug with:

spice-glib-0.26-7.el7.x86_64
spice-gtk3-0.26-7.el7.x86_64
virt-viewer-2.0-7.el7.x86_64
spice-glib-devel-0.26-7.el7.x86_64
Comment 12 errata-xmlrpc 2016-11-04 01:12:18 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.

https://rhn.redhat.com/errata/RHBA-2016-2229.html
Note You need to log in before you can comment on or make changes to this bug.