Selected option "Enable WAN" at Console dialogue cannot be undone for Windows guests. rhevm-spice-client-x64-msi-4.0-2.el7ev.noarch * Mon Jun 13 2016 Uri Lublin <uril> - 4.0-2 - mingw-virt-viewer 2.0-10 - mingw-spice-gtk 0.31-2 RHEV 4.0.0-19 How reproducible: always 1. Have a VM with a Windows guest. 2. Open "Console options" for the VM. 3. Check "Enable WAN options". 4. Connect to the VM with remote-viewer. 5. Make sure that "WAN options" are applied. (Number of colours is reduced to 16 bit). 6. Close connection. 7. un-check "Enable WAN options". 8. Connect to the VM again. All further connections to VM will have reduced colours, disabled animation, etc.. It is also a true for any connection to the VM from different places. Expected results: un-checked "Enable WAN options" should connect to the VM without reduced colours.
Still reproducible with rhv4.1.1.2-0.1.el7 spice-client-msi-x86-4.1-6.el7ev.noarch but reproducibility is not 100% but about 80%.
Still reproducible with rhv4.2.1.6-0.1.el7 RHV-toolsSetup_4.2_2.iso
Should be fixed automatically as soon as BZ 1543881 is fixed. Marking this as TestOnly. Also fixing BZ 1543538 should solve the "workaround" to resize the Window.
"Enable WAN" option set some configurations in remote-viewer such as color-depth which is deprecated as it rely on driver implementations that are lacking or also deprecated/limited from OS. E.g: color-depth only works below 32 bpp up to Windows 7 and doesn't work on Linux. > Expected results: un-checked "Enable WAN options" should connect to the VM without reduced colours. I wonder if remote-viewer should be the one trying to tweak guest configurations? I would guess that qemu guest agent is a better tool for that. Would be good to list the options/tweaks that are needed for the 'Enable WAN' option as some of this configs in spice-gtk are going away soon.
This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.
(In reply to Sandro Bonazzola from comment #5) > This bug has not been marked as blocker for oVirt 4.3.0. > Since we are releasing it tomorrow, January 29th, this bug has been > re-targeted to 4.3.1. Please, justify the latest assignment to rh-spice-bugs before making it. It looks like no investigations took place for 2.5 years. What about 1543881 and the proposal in https://bugzilla.redhat.com/show_bug.cgi?id=1543881#c2 ?
4.3.1 has been released a while ago, re-targeting to 4.3.3. Re-assigned from bugs to rh-spice-bugs because this bug had oVirt team set to spice and nobody looking at it since 2018-12-11. If nobody in spice team is going to handle this, assuming comment #3 is right, you can close this as wontfix being both referenced bugs closed as wontfix.