Bug 1336327

Summary: sigsegv on file transfer while killing the agent
Product: Red Hat Enterprise Virtualization Manager Reporter: Victor Toso <victortoso>
Component: mingw-virt-viewerAssignee: Default Assignee for SPICE Bugs <rh-spice-bugs>
Status: CLOSED ERRATA QA Contact: SPICE QE bug list <spice-qe-bugs>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: cfergeau, fidencio, gklein, lsurette, rbalakri, rh-spice-bugs, spice-qe-bugs, srevivo, tpelka, trichard, uril
Target Milestone: ovirt-4.0.0-rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mingw-spice-gtk-0.31-2.el7ev mingw-virt-viewer-2.0-10.el7ev rhevm-spice-client-4.0-2 Doc Type: Bug Fix
Doc Text:
Previously, when the Guest Agent was being killed at the same time as an ongoing file-transfer operation, the client crashed due to accessing the wrong error pointer, which was NULL. Now it accesses the correct error pointer, which is not NULL, so the client does not crash anymore.
Story Points: ---
Clone Of: 1336321 Environment:
Last Closed: 2016-08-23 20:50:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Spice RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1336321    
Bug Blocks:    

Description Victor Toso 2016-05-16 08:01:20 UTC
+++ This bug was initially created as a clone of Bug #1336321 +++

Description of problem:
Client's crash on a file-transfer while killing the agent in the guest

Version-Release number of selected component (if applicable):
spice-gtk 0.31-2 el7

How reproducible:
100%

Steps to Reproduce:
1. Drag and drop a file from client to guest
2. Kill spice-vdagentd
3. See remote-viewer crashes

Actual results:
Client crashes.

Expected results:
No crashes!

Additional info:
Fixed upstream by
https://cgit.freedesktop.org/spice/spice-gtk/commit/?id=a61c1ff0ac34fded8f71e528594c3f548479cd44

Comment 4 errata-xmlrpc 2016-08-23 20:50:53 UTC
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.

https://rhn.redhat.com/errata/RHEA-2016-1681.html