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 1728756 - Rebase libX11 in 8.2
Summary: Rebase libX11 in 8.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libX11
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.2
Assignee: Adam Jackson
QA Contact: Desktop QE
URL:
Whiteboard:
: 1728794 (view as bug list)
Depends On:
Blocks: 1755139
TreeView+ depends on / blocked
 
Reported: 2019-07-10 15:37 UTC by Adam Jackson
Modified: 2020-12-20 07:23 UTC (History)
3 users (show)

Fixed In Version: libX11-1.6.8-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:41:21 UTC
Type: ---
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1633 0 None None None 2020-04-28 15:41:45 UTC

Description Adam Jackson 2019-07-10 15:37:29 UTC 
Rebase libX11 in 8.2
Comment 1 Adam Jackson 2019-07-10 17:42:58 UTC 
*** Bug 1728794 has been marked as a duplicate of this bug. ***
Comment 3 Olivier Fourdan 2019-11-26 14:53:06 UTC 
Note: libX11-1.6.8 triggers a crash in xts (Xlib7) testing `XCopyColormapAndFree()`:

520|4 5 00014017 1 2|Assertion XCopyColormapAndFree-5.(A)
520|4 5 00014017 1 3|When a colourmap argument does not name a valid colourmap,
520|4 5 00014017 1 4|then a BadColor error occurs.
520|4 5 00014017 1 5|METH: Create a bad colourmap by creating and freeing a colourmap.
520|4 5 00014017 1 6|METH: Call test function using bad colourmap as the colourmap argument.
520|4 5 00014017 1 7|METH: Verify that a BadColor error occurs.
520|4 5 00014017 1 8|unexpected signal 6 (SIGABRT) received
220|4 5 2 15:05:53|UNRESOLVED
410|4 5 1 15:05:53|IC End
510|4|system 0: Abandoning testset: caught unexpected signal 11 (SIGSEGV)

This is related to https://gitlab.freedesktop.org/xorg/lib/libx11/merge_requests/12 which was ained at fixing https://gitlab.freedesktop.org/xorg/lib/libx11/issues/94

Specifically, reverting the bits in `XCopyColormapAndFree` (https://gitlab.freedesktop.org/xorg/lib/libx11/blob/master/src/CopyCmap.c#L43) fixes the crash in xts.
Comment 4 Adam Jackson 2019-12-11 20:29:17 UTC 
Workaround filed upstream:

https://gitlab.freedesktop.org/xorg/lib/libx11/merge_requests/31

I'm not convinced that workaround is perfect, but it's certainly good enough for 8.2 I think.
Comment 7 errata-xmlrpc 2020-04-28 15:41:21 UTC 
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.

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