RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1436589 - RFE: Handle closed connections/channels
Summary: RFE: Handle closed connections/channels
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-gtk
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: 8.1
Assignee: Default Assignee for SPICE Bugs
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On: 1719736
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-28 09:04 UTC by David Jaša
Modified: 2020-09-15 12:03 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-01 13:18:47 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description David Jaša 2017-03-28 09:04:22 UTC
Description of problem:
Spice-server handles stale connections for quite some time already: it closes them. On the other hand, spice-gtk doesn't handle them in any way: it either just stops transfering the data for non-main channels, or the whole remote desktop "freezes". This happens frequently with proxies or NATs with agressive timeouts.
Users don't expect such an experience, when e.g. everything appears fine but sound from VM suddenly doesn't reach the client, or conversely, music keeps playing but display goes stale.

Spice-gtk should therefore handle closed connections. The most "expected" way is IMO to reconnect non-main channels and for main channel, either exit (like when VM shuts down) or give some non-intrusive message that connection broke.

Version-Release number of selected component (if applicable):
el7:
  spice-gtk3-0.33-1.el7.x86_64 
  virt-viewer-5.0-2.el7.x86_64
w10:
  VirtViewer v2.0-208
  mingw32-spice-gtk3-0.31-6.el7ev.noarch

How reproducible:
always

Steps to Reproduce:
1. connect to a VM through a network/proxy with short TCP connection timeouts
2.
3.

Actual results:
as various idle channels disconnect, respective parts of client stop working

Expected results:
client reconnects the channels or exits

Additional info:

Comment 1 Christophe Fergeau 2017-03-28 09:55:33 UTC
(In reply to David Jaša from comment #0)
> Actual results:
> as various idle channels disconnect, respective parts of client stop working
> 
> Expected results:
> client reconnects the channels or exits
> 

Alternatively, we could make sure no channels get disconnected if there is activity on one of them. Reconnecting is made a bit harder if a ticket was initially required, I don't know what would happen if we disconnect/reconnect a usbredir channel with an idle USB device redirected, ...

Comment 2 David Jaša 2017-03-28 13:53:44 UTC
(In reply to Christophe Fergeau from comment #1)
> Alternatively, we could make sure no channels get disconnected if there is
> activity on one of them. Reconnecting is made a bit harder if a ticket was
> initially required, I don't know what would happen if we
> disconnect/reconnect a usbredir channel with an idle USB device redirected,
> ...

True.

This bug may also be mitigated by fixing of bug 1428804, if that doesn't turn out (for example, I've experienced disconnections over WAN even when using versions that enable TCP_KEEPALIVE), probably by sending RED_PING after some inactivity period.

Comment 5 Martin Tessun 2019-11-25 08:22:20 UTC
This sounds like a huge usability improvement. Having some feedback on disconnected channels is helpful, so the use knows what is going on. Even in case the user would need to restart his viewer to get the reconnect it is better than having no feedback on what is happening.


Note You need to log in before you can comment on or make changes to this bug.