Created attachment 1006761 [details]
virt-viewer debug log
Description of problem:
Disabled display comes out again after uncheck it
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Prepare a rhel guest with spice + qxl + spicevmc
2. Configure the guest with only 1 display, use virt-viewer to connect it.
3. View - > Displays - > Check Display2,3,4 all.
4. Uncheck Display 3.(May need try several times)
Display 3 appear again.
Uhchecked display 3 should not appear again.
1. I will attach virt-viewer debug log.
Could you check if it's a regression? thanks
Can you get a spice log as well? It's not being so easy to reproduce it here ...
(run virt-viewer --debug --spice-debug ...)
(In reply to Fabiano Fidêncio from comment #3)
> Can you get a spice log as well? It's not being so easy to reproduce it here
> (run virt-viewer --debug --spice-debug ...)
Yes, it's not easy to reproduce it, may you need try check/uncheck display for several times.
Just now i reproduce it again and i will attach debug log again, thanks.
# virt-viewer 6-x64 --debug --spice-debug |& tee >all_debug
Created attachment 1007069 [details]
with --debug --spice-debug
I cannot reproduce the problem with a newer version vdagent.
I'm providing you a scratch build (with the possible fix included). Can you, please, try to reproduce the issue with the provided build?
Hi Fabiano Fidêncio,
I can reproduce this issue:
with guest installed by iso: RHEL-6.6-20140926.0-Server-x86_64-dvd1.iso
pkg version: spice-vdagent-0.14.0-4.el6.x86_64
Then tried with scratch build:
1. Update pkg spice-vdagent both on host and guest to new version:
# rpm -q spice-vdagent
2. Use virt-viewer to connect guest and do as Comment 0 described:
# virt-viewer 6-x64
Result: Tried several times but cannot reproduce bug issue any more.
Okay. Just for the record, the patch that solves the problem is 9ae51f3702b1fc0d2747e44474c87a818d1e8ec3, on linux vd-agent.
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.