Description of problem:
with RHEV-M's "full screen" or CLI "--full-screen=auto-conf", secondary monitor of the guest keeps flashing (as if the resolution of it was changing in the loop - to the same one)
Version-Release number of selected component (if applicable):
mingw-virt-viewer-0.5.3-24 / Windows XP
vdagent-win -16 (Windows 7 64b)
Steps to Reproduce:
1. have a windows VM with 2+ monitor but just one active
2. connect to the VM from 2+ monitor client with RHEV-M "Full screen" checked or with "--full-screen=auto-conf" on CLI
after the connection, the second monitor keeps flashing and can not be effectively used because any mouse work is interrupted every other second
second monitor flashes just once at guest monitor resolution is adjusted to client one
*** Bug 952691 has been marked as a duplicate of this bug. ***
Contrary to Vimal's setup, the first monitor was still perfectly usable but the secondary kept flashing. Things were OK when going fullscreen from windowed mode.
very likely vdagent bug, due to custom resolution regression when enabling extra monitors.
Please grab the vdagent.log, thanks
Created attachment 738926 [details]
2100::INFO::2013-04-23 06:15:10,062::VDService::main::***Service started***
2100::INFO::2013-04-23 06:15:10,062::VDService::execute::Active console session id: 1
2100::INFO::2013-04-23 06:15:10,070::VDService::execute::Connect state: 0
Sent patch to fix this on spice-gtk side:
It would be worth to fix vdagent too to not reconfigure monitor with same config, but it's another story.
(In reply to comment #12)
> Sent patch to fix this on spice-gtk side:
> It would be worth to fix vdagent too to not reconfigure monitor with same
> config, but it's another story.
will give it a look from vdagent side.
This is verified with RHEV-M 3.2 (sf14) and virt-viewer 0.5.3-23.
Wrong bug verified.
This is now verified with spice-client-msi-3.2-10 and mingw-virt-viewer 0.5.3-25.
*** Bug 922391 has been marked as a duplicate of 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.