Hide Forgot
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).
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.
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/