Red Hat Bugzilla – Bug 985898
Too many windows open with fullscreen=auto-conf
Last modified: 2014-01-21 09:46:39 EST
Description of problem: Virt-viewer sometimes opens one too many windows when fullscreen is configured when connecting to a windows guest Version-Release number of selected component (if applicable): mingw-virt-viewer-0.5.3-28 How reproducible: 100 % Steps to Reproduce: 1. Connect to a windows guest without fullscreen autoconf 2. Open several additional monitors (more than physical on client) 3. close the session. 4. Connect to the guest again, this time with autoconf enabled Actual results: First n monitors will be correctly open on first n physical monitors, but at least one addition guest monitor will be open partially overlapping one of the others Expected results: Guest should have at most the same number of monitors as client.
grr, hard bug to fix it seems. there is no relation between client monitor config request, and current received configuration (in fact 1 request, can trigger n server monitor config reply that may be related or not), so we will have to hack something that might have undesirable side effects. So what we could do is make sure to disable monitors that don't fit in fullscreen, I have been trying to do that... The bug doesn't seem to easy to reproduce with the linux build, I think it shows that this is somehow also racy.
weird, I can't reproduce on XP either, but with win7 100%..
Sent patch series fixing this: https://www.redhat.com/archives/virt-tools-list/2013-July/msg00120.html
Tried 0.5.6-9 and it doesn't fix it. Same issue.
(In reply to Tomas Jamrisko from comment #5) > Tried 0.5.6-9 and it doesn't fix it. Same issue. are you sure you tried with auto-conf? if not autoconf, it's expected we open as many windows as guest monitors.
This bug is currently attached to errata RHEA-2013:15512. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
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-0034.html