remote-viewer hangs with --spice-debug option on .vv file that has fullscreen=1 Client is Windows7SP1. rpm -qf /usr/share/spice/virt-viewer-x64.msi rhevm-spice-client-x64-msi-3.6-6.el6.noarch rpm -q --changelog rhevm-spice-client-x64-msi * Mon Jan 04 2016 Uri Lublin <uril> - 3.6-6 - mingw-virt-viewer 2.0.8 - mingw-spice-gtk 0.26-10 - mingw-libusbx 1.0.20-1 - spice-usbdk-win 1.0-10 - Send requests to usbdk asynchronously (rhbz#1144043) Rhevm 3.6.4.1-0.1.el6 Host is Rhel7.2.z kernel-3.10.0-327.10.1.el7.x86_64 qemu-kvm-rhev-2.3.0-31.el7_2.10.x86_64 How reproducible: 100% Steps to Reproduce: 1. Go to RHEVM userportal 2. Edit console options for VM to open in fullscreen mode 3. Press CONSOLE 4. Save .vv file 5. Open powershell 6. Run remote-viwer with next command: .\remote-viewer.exe --spice-debug 'C:\Users\astepano\Downloads\console.vv'
Can you confirm if this is related to bug 1287139?
I can't reproduce the issue at all with a fresh installed Windows 7 machine using mingw-virt-viewer 2.0.8.
Please, take a look on https://bugzilla.redhat.com/show_bug.cgi?id=1323092#c8
This bug is about one window and one virtual display in remote-viewer. Are you sure that the memory is the issue?
No, I'm not 100% sure it's related to the memory issue. But I would like to know if it happens with the proper layout setup.
Could you please elaborate what is "proper layout setup" ?
A "proper layout setup" is something that works according to: https://bugzilla.redhat.com/show_bug.cgi?id=1275539#c12 I won't close this bug. I just want to take a look on it after the memory issues get solved. Does it work for you?
This bug is about one virtual display. Client's screen resolution is 1280x1024. I _can_ connect to VM in fullscreen mode. The bug is about --spice-debug option. Could you please explain why do you refer to other bugs?
Seems it doesn't work for you. :-\ My feeling is that these bugs are all related. Eduardo has the same feeling. You can see that by comment 5 and comment 1, respectively. While I can't reproduce, can you paste exactly the steps you did for reproducing this bug? AFAIR, while in your place, you played with fullscreen/exit fullscreen after the first try (which, was not reprocible).
I cannot reproduce the bug using the same environment. I tried many times.
I cannot reproduce it using the same environment.