Bug 1565096
| Summary: | gdkscreen-x11: Don't try to calculate a refresh rate when the XRRModeInfo doesn't have one [rhel-7.5.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Oneata Mircea Teodor <toneata> |
| Component: | gtk3 | Assignee: | Debarshi Ray <debarshir> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | Jaroslav Klech <jklech> |
| Priority: | high | ||
| Version: | 7.4 | CC: | alanm, dbasant, debarshir, jklech, jkoten, pbhoot, tpelka, vbudikov |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | gtk3-3.22.26-4.el7_5 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, certain types of the X Server program, such as Windows Exceed and xrdp, caused errors in the GTK+ library. As a consequence, GTK+ applications terminated unexpectedly when run against the affected X Servers. This update modifies GTK+ to avoid division by zero when there is no adequate refresh rate. As a result, GTK+ applications successfully start when run against the affected X Servers.
|
Story Points: | --- |
| Clone Of: | 1502788 | 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: | 1502788 | ||
| Bug Blocks: | |||
|
Description
Oneata Mircea Teodor
2018-04-09 11:27:59 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 content. I have modified it a little bit. Could you, please, have a look at it, whether it is still correct content-wise? Thanks Jaroslav (In reply to Jaroslav Klech from comment #5) > thank you for the content. I have modified it a little bit. Could you, > please, have a look at it, 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 |