Red Hat Bugzilla – Bug 1022608
After switching from full-screen using Shift-F11, arbitrary resolution doesn't work
Last modified: 2016-03-09 15:04:17 EST
Description of problem: After running virt-viewer from RHEVM User Portal in full-screen mode and switching to window mode using the Shift-F11 keyboard shortcut, the guest resolution can no longer be changed by resizing the remote-viewer window. Version-Release number of selected component (if applicable): RHEVM 3.3 is19 Client: Windows 7 32bit mingw-virt-viewer-0.5.6-8.el6_4 How reproducible: Always Steps to Reproduce: 1. Set Open in Full Screen in Console options of VM 2. Open the console -> VM opens in full screen mode 3. Use Shift-F11 to switch to window mode Actual results: The guest resolution is not appropriately changed to match the window size. Further manual changes of the remote-viewer window are ignored as well. Expected results: Guest resolution changes to match the window dimensions. Additional info: Using the button at the top of the screen to exit from full screen mode works fine. The bug only occurs when keyboard shortcut Shift-F11 is used.
I can reproduce, but it doesn't always happen. If I leave fullscreen with the button once, then the keyboard shortcut works. Weird..
the bug is fixed in upstream, where the fullscreen/unfullscreen logic has been modified. I think we should wait for next rebase.
rebase proposed for 3.5 (Bug 1103366)
I still can reproduced the bug in following steps: 1. Set Open in Full Screen in Console options of VM 2. Open the console -> VM opens in full screen mode 3. Use Shift-F11 to switch to window mode -> resolution is adjusted. 4. Use Shift-F11 to switch to full-screen mode -> resolution is not adjusted. It works properly when using virt-viewer full-screen button instead of keyboard shortcut.
Posted a patch: https://www.redhat.com/archives/virt-tools-list/2014-September/msg00233.html
Rebase done -- moving to MODIFIED
Changed doc_text field to - due to "no doc required" message.
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. https://rhn.redhat.com/errata/RHEA-2016-0377.html