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 644292 - [abrt] spice-client-0.4.2-18.el6: __strncpy_ssse3: Process /usr/libexec/spicec was killed by signal 11 (SIGSEGV)
Summary: [abrt] spice-client-0.4.2-18.el6: __strncpy_ssse3: Process /usr/libexec/spice...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: spice-client
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Uri Lublin
QA Contact: Desktop QE
URL:
Whiteboard: abrt_hash:7649104cf9b9ccbdd40ac973ab5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-19 11:08 UTC by Lubos Kocman
Modified: 2011-06-15 14:48 UTC (History)
3 users (show)

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.
Clone Of:
: 680740 (view as bug list)
Environment:
Last Closed: 2011-05-19 13:15:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
File: backtrace (57.66 KB, text/plain)
2010-10-19 11:08 UTC, Lubos Kocman
no flags Details
2nd backtrace (232.54 KB, text/plain)
2010-11-18 15:16 UTC, Lubos Kocman
no flags Details
~/.spice/spice.log with DEBUG mode (1.73 KB, application/octet-stream)
2010-11-18 15:19 UTC, Lubos Kocman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0583 0 normal SHIPPED_LIVE libcacard and spice-client bug and enhancement update 2011-05-19 09:37:34 UTC

Description Lubos Kocman 2010-10-19 11:08:48 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/spicec --controller
comment: If this issue will happen again I'll try to provide some step-by-step reproducer. No reproducer is currently available.
component: spice-client
crash_function: __strncpy_ssse3
executable: /usr/libexec/spicec
kernel: 2.6.32-71.el6.x86_64
package: spice-client-0.4.2-18.el6
rating: 4
reason: Process /usr/libexec/spicec was killed by signal 11 (SIGSEGV)
release: Red Hat Enterprise Linux Workstation release 6.0 (Santiago)
time: 1287067460
uid: 501

Comment 1 Lubos Kocman 2010-10-19 11:08:50 UTC
Created attachment 454327 [details]
File: backtrace

Comment 3 Lubos Kocman 2010-11-18 15:16:24 UTC
Created attachment 461319 [details]
2nd backtrace

Another backtrace file related to the same issue

Comment 4 Lubos Kocman 2010-11-18 15:19:57 UTC
Created attachment 461320 [details]
~/.spice/spice.log with DEBUG mode

Comment 5 Hans de Goede 2011-02-27 12:38:09 UTC
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.

Comment 6 Uri Lublin 2011-03-01 14:46:06 UTC
Going to fix it in 6.1 after all

Comment 7 Hans de Goede 2011-03-02 16:28:32 UTC
A build containing a fix for this has been done, moving to modified.

Comment 9 Lubos Kocman 2011-04-19 14:57:46 UTC
Never happened to me again. Moving to verified. Checked on spice-client-0.8.0-2.el6.x86_64

Comment 10 Tomas Capek 2011-05-17 11:40:31 UTC
    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.

Comment 11 errata-xmlrpc 2011-05-19 13:15:15 UTC
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


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