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 680740 - [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 WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libX11
Version: 6.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Adam Jackson
QA Contact: Desktop QE
URL:
Whiteboard: abrt_hash:7649104cf9b9ccbdd40ac973ab5...
Depends On:
Blocks: 842499
TreeView+ depends on / blocked
 
Reported: 2011-02-27 12:40 UTC by Hans de Goede
Modified: 2017-12-06 11:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 644292
Environment:
Last Closed: 2017-12-06 11:25:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 2 Hans de Goede 2011-02-27 12:48:32 UTC 
I cloned bug 644292 to this one, because the second backtrace in that bug:
https://bugzilla.redhat.com/attachment.cgi?id=461319

Is completely unrelated to the first one. The second bug is crashing deep inside libX11 / libxcb, this is likely related to spicec accessing libX11 from multiplethreads. Note that upstream libX11 + libxcb have fixes espp. targetting multi thread apps calling Xsync, and upstream spicec has patches to add proper
locking to X11 calls as that is needed with the newer version, otherwise it may hang in some cases (as doucmented in the upstream libX11 / libxcb commits).
Comment 3 RHEL Program Management 2011-02-27 12:58:21 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 5 Jan Kurik 2017-12-06 11:25:24 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.