Hide Forgot
Created attachment 791413 [details] Left display is fullscreen guest, right one is maximized. Notice how left side of the primary display appears in both windows Description of problem: Opening two monitors on a dual head setup and switching one of them to fullscreen can result in its corruption -- displaying parts of the other window Version-Release number of selected component (if applicable): spice-gtk-0.20-5.el6.x86_64 virt-viewer-0.5.6-7.el6.x86_64 spice-vdagent-0.14.0-1.el6.x86_64.rpm How reproducible: Fairly often Steps to Reproduce: 1. Get dual head client with different resolutions of windows 2. Open two displays on guest (have position of primary displays swapped between client and guest) 3. Switch the one on secondary display of client to fullscreen Actual results: See screenshot
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
I can reproduce with: virt-viewer-0.5.6-8.el6.x86_64 1. Get dual head client with different resolutions of windows 2. Open two displays with full screen. 3. Click leave screen on the primary display, then change it to fullscreen again. Result: The primary display will cover part of the other display.And check the "Display Preferences", one display overlaps other one.
I've pushed several patches upstream that should fix this particular issue.
Jonathon, please update bug status, fill the Doc Text. thanks
I can reproduce with: virt-viewer-0.5.6-8.el6.x86_64 Verify with virt-viewer-0.6.0-5.el6.x86_64 1. Get dual head client with different resolutions of windows 2. Open two displays on guest (have position of primary displays swapped between client and guest) 3. Switch the one on secondary display of client to fullscreen Result: two displays have no overlap. Also test as comment 3. Result is expected, two displays have no overlap. As the result, VERIFIED this bug.
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. http://rhn.redhat.com/errata/RHBA-2014-1379.html