Bug 1005411

Summary: Input grab misbehavior when showing/hiding second display
Product: [Community] Virtualization Tools Reporter: Jonathon Jongsma <jjongsma>
Component: virt-viewerAssignee: Daniel Berrangé <berrange>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: xen-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-21 15:12: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:

Description Jonathon Jongsma 2013-09-06 20:30:43 UTC
Description of problem:
When hiding and showing the second display of a guest, sometimes the input of the host gets into a strange state which doesn't allow you to move windows around or open menus on certain windows, etc.

Version-Release number of selected component (if applicable):
git commit 67ed4dff9829a1d957aebba9223028f6805dfafb

How reproducible:
always

Steps to Reproduce:
1. Set up a guest with 2 displays
2. Connect to guest with virt/remote-viewer.  2 display windows should be opened.
3. Click "View > Displays > Display 2" to hide the second display window
4. Now repeate step 3 to open the second display window again

Actual results:
The second display window is displayed, but that window cannot be moved or resized, and e.g. the gnome-shell overview cannot be activated

Expected results:
Window is displayed and functional

Additional info:
Activating a menu in the second display window seems to break the mouse grab and the window can then be moved / resized, etc.  The issue also doesn't happen if you run the program with SPICE_NOGRAB=1

Comment 1 Daniel Berrangé 2019-03-21 15:12:43 UTC
There's been lots of fixes related to multi-monitor support since this was filed. I can't claim I know a specific fix that matches the bug description, but I'm going to close it on balance of probabilities as leaving it open isn't doing much better. Feel free to reopen if needed.