Bug 810583
Summary: | disconnect() method of spice-xpi does not kill client | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | David Jaša <djasa> |
Component: | spice-xpi | Assignee: | Peter Hatina <phatina> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 6.3 | CC: | acathrow, dblechte, dyasny, mkrcmari, tsmetana, uril |
Target Milestone: | rc | ||
Target Release: | 6.4 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | spice-xpi-2.7-21.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-21 10:57:54 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: | 815674 | ||
Bug Blocks: |
Description
David Jaša
2012-04-06 21:08:26 UTC
In current state, we are not able to solve this in a reasonable way. Now we have alternatives, so /usr/libexec/spice-xpi-client points to 2 shell scripts, which run either spicec or remote-viewer. The problem is, that if I signal (by SIGTERM) spice-xpi-client, the client does not die -- caused by the structure of the script(s). The best solution could be: to signal a process group, where the parent is the mentioned spice-xpi-client. Rhel 6.3 in current state suffers from a bug, where is is not able to signal a process group. I already filed that bug. Moving to 6.4 for now: First, it depend on https://bugzilla.redhat.com/show_activity.cgi?id=815674; and second, spice devel is focusing on virt-vierwer as the spicec replacement. Fixed. 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. http://rhn.redhat.com/errata/RHBA-2013-0459.html |