Red Hat Bugzilla – Bug 1021618
resolution set by user inside the VM gets reverted to client resolution when in full screen
Last modified: 2014-01-21 09:47:27 EST
Description of problem:
resolution set by user inside the VM gets reverted to client resolution when in full screen. This is essentially a regression of bug 864929 (and clones) that is in 3.3 client (but not in 6.5 client). The regression occurs always when "auto resize" is enabled with the only exception when the client is launched with --full-screen=auto-conf and the client is not subsequently unmaximized.
The current behaviour of windows client is bad IMO because it overrides explicit user action no no really good reason (when users want to revert to client resolution, they are able to do that through window/fulscreen cycle or in ideal world, with ctrl+0 shortcut)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. connect to a guest with agent, go to full-screen
2. in the guest, change resolution to something else
resolution gets reverted right away
resolution is left as-is (as in RHEL 6.5 client or when connected with --full-screen=auto-conf)
added patches from Bug #864929
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:
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.