Bug 816241

Summary:	Handle disconnections exposed by spice-gtk
Product:	Red Hat Enterprise Linux 6	Reporter:	David Jaša <djasa>
Component:	virt-viewer	Assignee:	Daniel Berrangé <berrange>
Status:	CLOSED WONTFIX	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.3	CC:	cfergeau, dblechte, desktop-qa-list, dyasny, gkong, jwu, mzhan, rwu, yupzhang, zpeng
Target Milestone:	beta
Target Release:	6.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-07-27 08:08:18 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:
Bug Depends On:	816231
Bug Blocks:

Description David Jaša 2012-04-25 15:27:56 UTC

Description of problem:
Handle disconnections exposed by spice-gtk. See the blocking bug for details.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 David Jaša 2012-04-25 15:35:50 UTC

Maybe a bit more info would be helpful. So in remote-viewer mode, an error pop-up should be created saying what went wrong. 

I'm not really sure what should happen when in virt-viewer mode (imagine one virt-viewer running, another one connecting to the same VM and stealing its desktop, first one detecting disconnect and thus reconnecting and taking display back and so forth...).

Comment 2 Daniel Berrangé 2012-04-25 15:42:34 UTC

I don't really see that there is anything that needs doing here. virt-viewer  & remote-viewer already handles guest disconnect messages from spice-gtk. By default they will exit unless the --reconnect flag was given, in which case they try to reconnect to the desktop

Comment 3 RHEL Program Management 2012-07-10 08:49:49 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 4 RHEL Program Management 2012-07-11 02:01:12 UTC

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 5 Daniel Berrangé 2012-07-26 17:32:36 UTC

Please provide more info on why current behaviour is wrong as per comment #2

Comment 6 David Jaša 2012-07-27 08:08:18 UTC

Seen with from a bit of distance, it looks like proposed changes solve the problem of tcp stream disruption only partialy if there is no heartbeat in spice protocol, so closing it myself as wontfix...