Red Hat Bugzilla – Bug 958966
Can not disable display through Windows screen resolution utility.
Last modified: 2013-11-21 03:08:56 EST
Description of problem: I have a 4 display guest running (W7-64) and I disconnect display 4 and then select apply or OK. As soon as that occurs the displays refresh and I still have display 4. If I click "save changes" my selection of disconnect display is changed back to "extend desktop to this display". Version-Release number of selected component (if applicable): Client: RHEL 6.4 64bit virt-viewer-0.5.2-18.el6_4.2.x86_64 spice-gtk-0.14-7.el6.x86_64 Guest: Windows 7 Enterprise 64bit RHEV-Tools 3.2.5 with vdagent-win-0.1-17 How reproducible: Every time. Steps to Reproduce: 1.Start connection to to that has 4 displays enabled. 2.When connected verify you have 4 displays. 3.Enter screen res utility, slect display 4, checge to disconne3ct this display and select ok or apply. 4.Then select keep changes and notice the display is still there and selection was reverted. Actual results: See steps. Expected results: Display disabled and selection retained. Additional info:
there has been a bit of back and forth, since there is no reliable way to know if a monitor is disabled by user settings or normally during reboot, we settled on keeping the display windows opened in bug 918997. Hence, the best way to remove a monitor is from virt-viewer display menu.
the bug has been best described in 868970 before reopening since rebase will improve behaviour
As the result of re-base, the rhel client behavior will match the one in mingw-virt-viewer
I can reproduce this bug: Version: virt-viewer-0.5.2-18.el6_4.2.x86_64 spice-gtk-0.14-7.el6.x86_64 Setps: As description. result: Can not disable display through Windows screen resolution utility Verify: virt-viewer-0.5.6-1.el6 spice-glib-0.20-1.el6.x86_64 spice-gtk-0.20-1.el6.x86_64 Steps: As description result: Can disable display through Windows screen resolution utility
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-2013-1578.html