Description of problem: When remote-viewer is started with options full-screen - true and adminconsole - false passed through controller - which can be achieved by choosing "Open in full-screen" in RHEVM User portal, The size of remote-viewer windows after switching from full-screen is "unreasonable" -> First primary window is resized to very small, every other window 2nd, 3rd ... have the resolution which equals to native resolution of client physical monitor where the window was opened in full-screen. Once remote-viewer is started from command line with --full-screen=auto-conf windows of remote-viewer after switching off from full-screen have "reasonable" size -> slightly lower than the native resolution of physical clients where the windows were opened - most likely resolution which It would have when opening spice session without full-screen option? Version-Release number of selected component (if applicable): Windows clients and guests (WinXP, Win7) vdagent-win 0.1-18 mingw-virt-viewer-0.5.3-28. How reproducible: Always Steps to Reproduce: 1. Log in RHEVM User portal from Windows client with two physical monitors. 2. Establish spice session to a Windows guest with spice-vdagent running. 3. Switch off from fullscreen. Actual results: Frist primary display of guest has very small size and the second display of guest keeps resolution It had - native resolution of client monitor Expected results: It should behave as It behaves when using command line --full-screen=auto-conf. Additional info:
This is most likely due to the original window size, and unfullscreen which restore the window geometry (since the fullscreen/auto-conf controller value come after the window is first shown) We don't want to workaround that behaviour of having original size restored for window mode Looking at gdk code, it seems we can remove that behaviour by deleting the "fullscreen-info" property on the underlying gdkwindow (this is not documented).
sent fixes to ML: https://www.redhat.com/archives/virt-tools-list/2013-July/msg00116.html
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