Bug 644292
| Summary: | [abrt] spice-client-0.4.2-18.el6: __strncpy_ssse3: Process /usr/libexec/spicec was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Lubos Kocman <lkocman> | ||||||||
| Component: | spice-client | Assignee: | Uri Lublin <uril> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | 6.0 | CC: | hdegoede, mkenneth, tcapek | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | abrt_hash:7649104cf9b9ccbdd40ac973ab598b9a64fdd603 | ||||||||||
| Fixed In Version: | spice-client-0.8.0-1.el6 | Doc Type: | Bug Fix | ||||||||
| Doc Text: |
When running the "spicec --controller" command without having set the SPICE_XPI_SOCKET environment variable, users could experience unexpected termination caused by a segmentation fault. This bug has been fixed and spicec now exits cleanly with an error message in this particular scenario.
|
Story Points: | --- | ||||||||
| Clone Of: | |||||||||||
| : | 680740 (view as bug list) | Environment: | |||||||||
| Last Closed: | 2011-05-19 13:15:15 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Lubos Kocman
2010-10-19 11:08:48 UTC
Created attachment 454327 [details]
File: backtrace
Created attachment 461319 [details]
2nd backtrace
Another backtrace file related to the same issue
Created attachment 461320 [details]
~/.spice/spice.log with DEBUG mode
The 2 backtraces seem to be completely unrelated: The first one is caused by calling spicec --controller without having set the SPICE_XPI_SOCKET environment variable. This can be caused by using a new spicec with an older spice-xpi. We will add a fix for to make spice exit cleanly with an error message in this case. We will use this bug to track this. Since this only happens when manually launching spicec, in a bad way or when using an outdated we are targeting 6.2 to fix this. The second backtrace seems to be a crash deep inside libX11 / libxcb, I'll clone this bug and re-assign the clone to libX11 for tracking this issue. Going to fix it in 6.1 after all A build containing a fix for this has been done, moving to modified. Never happened to me again. Moving to verified. Checked on spice-client-0.8.0-2.el6.x86_64
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When running the "spicec --controller" command without having set the SPICE_XPI_SOCKET environment variable, users could experience unexpected termination caused by a segmentation fault. This bug has been fixed and spicec now exits cleanly with an error message in this particular scenario.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0583.html |