Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 871573

Summary:	when reconnecting one of guest displays via menu, it's screen is black until disabled and enabled again in the guest
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	David Jaša <djasa>
Component:	mingw-virt-viewer	Assignee:	Marc-Andre Lureau <marcandre.lureau>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.1.0	CC:	acathrow, cfergeau, dblechte, mkrcmari, pvine
Target Milestone:	---
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	mingw-virt-viewer-0.5.3-24.el6ev	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-24 17:25:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Jaša 2012-10-30 18:25:46 UTC

Description of problem:
when reconnecting one of guest displays via menu, it's screen is black until disabled and enabled again in the guest

Version-Release number of selected component (if applicable):
client from rhevm-spice-client-x86-cab-3.1-4
windows guest

How reproducible:
always

Steps to Reproduce:
1. connect to a 2-monitor windows VM from windows client
2. in r-v menu, disable second monitor (View -> Displays -> Display n)
3. reenable the monitor in the same way
  
Actual results:
the monitor is unusable until switched off by guest display configuration tool and switched on again

Expected results:
the monitor is usable right away

Additional info:
rhel r-v works just fine

Comment 1 Marc-Andre Lureau 2012-10-30 21:52:56 UTC

(In reply to comment #0)
> Additional info:
> rhel r-v works just fine

rhel 6.4 differes a lot regarding multi-monitor handling, have you tried with r-v from rhel 6.3?

Comment 2 David Jaša 2012-10-31 09:06:22 UTC

rhel 6.3 r-v works fine too.

Comment 3 David Jaša 2012-11-02 13:23:44 UTC

fixed in mingw-virt-viewer-0.5.3-14 (spice-client-msi-3.1-6)

Comment 4 David Jaša 2012-11-02 14:55:58 UTC

Interesting, I hit the bug again without any change to test setup. Maybe the fix was premature...

Comment 5 Marc-Andre Lureau 2012-11-02 15:19:51 UTC

(In reply to comment #4)
> Interesting, I hit the bug again without any change to test setup. Maybe the
> fix was premature...

ok, please try to give as much details as possible. What is the guest OS, version, presence/version of agents & qxl driver. Can you reproduce with Linux. Is it 50% reproducible etc. thanks

Comment 6 David Jaša 2012-11-02 16:24:40 UTC

(In reply to comment #5)
> (In reply to comment #4)
> > Interesting, I hit the bug again without any change to test setup. Maybe the
> > fix was premature...
> 
> ok, please try to give as much details as possible. What is the guest OS,
> version,

Windows; XP and 7x32

> presence/version of agents & qxl driver. 

both are tooled with 3.1-8, that means:
qxl-win -12
vdagent-win -12

> Can you reproduce with
> Linux. Is it 50% reproducible etc. thanks

the bug occurs neither in 6.4 nor 6.3 virt-viewer.

Comment 7 David Blechter 2013-02-06 21:30:01 UTC

no pm ack for 3.2, revert devel ack to ?

Comment 8 Andrew Cathrow 2013-02-19 22:35:38 UTC

Need to consider for 3.2.z

Comment 10 Marc-Andre Lureau 2013-03-26 11:58:41 UTC

David, this is very likely a dup of bug 922283. Could you try with vdagent-win-0.1-16 ? thanks

Comment 11 David Jaša 2013-04-12 14:57:03 UTC

with virt-viewer -23 and vdagent -16, the bug is a bit different: only the "connecting <...>" message is gone but the guest monitor in question is still unusable.

Comment 13 David Jaša 2013-04-15 15:18:10 UTC

mingw-virt-viewer -24 works correctly at last.

"unusable" was that the monitor seemed to work from within the guest but the client showed just black canvas.

Comment 14 David Blechter 2013-04-24 17:25:04 UTC

it sounds like the problem is not present in the latest build. Likely "under influence" of other bug fixes. Closed as CURRENTRELEASE