Bug 1566585
| Summary: | epoxy_glx_version & friends crash without GLX and hinder gtk3 startup [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | libepoxy | Assignee: | Debarshi Ray <debarshir> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | unspecified | Docs Contact: | Jaroslav Klech <jklech> |
| Priority: | high | ||
| Version: | 7.6 | CC: | alanm, debarshir, jklech, tpelka |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | libepoxy-1.3.1-2.el7_5 | Doc Type: | Bug Fix |
| Doc Text: |
Due to lack of support for OpenGL Extension to X Windows System (GLX) extensions, GTK+ applications terminated unexpectedly when run against certain X Server programs, such as X2Go and Xvfb. This update modifies the libepoxy library to work around the absence of GLX support. As a result, GTK+ applications start successfully when run against the mentioned X Servers.
|
Story Points: | --- |
| Clone Of: | 1566101 | Environment: | |
| Last Closed: | 2018-05-14 16:11:10 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: | |||
| Bug Depends On: | 1566101 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-04-12 14:54:43 UTC
Hi Debarshi, Please, could you provide info to document this bug in CCFR structure (cause, consequence, fix, result)? Thank you Jaroslav Hello Debarshi, thank you for the doc text content. I tweaked it a little bit. Could you tell me whether it is still correct content-wise, please? Thanks Jaroslav (In reply to Jaroslav Klech from comment #6) > thank you for the doc text content. I tweaked it a little bit. Could you > tell me whether it is still correct content-wise, please? Yes, looks good to me. Hi Debarshi, I have made some modifications to the doc_text. Could you, please, review it and tell me whether it is still correct content-wise? Thank you Jaroslav (In reply to Jaroslav Klech from comment #8) > I have made some modifications to the doc_text. Could you, please, review it > and tell me whether it is still correct content-wise? Yes, looks good to me. 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-2018:1393 |