Bug 1168600
| Summary: | [glib 2.40 regression] Attempt to add property xxx after class was initialised | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Milan Crha <mcrha> |
| Component: | glib2 | Assignee: | Colin Walters <walters> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.1 | CC: | ayadav, tpelka, vbenes, yacao |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The version of glib2 in 7.1 emitted warning messages when programs added GObject properties after the class was initialized.
Consequence: A warning message appeared, but the program continued to function.
Fix: This functionality was un-deprecated due to backwards compatibility concerns.
Result: No error messages about properties appear.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 08:15:19 UTC | Type: | Bug |
| 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: | 1104372 | ||
| Bug Blocks: | |||
|
Description
Milan Crha
2014-11-27 11:29:46 UTC
Agreed, let's remove the warning. It's similar to https://bugzilla.redhat.com/show_bug.cgi?id=1104372#c11 This will be addressed with 2.42. https://bugzilla.gnome.org/show_bug.cgi?id=698614 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://rhn.redhat.com/errata/RHBA-2015-2116.html *** Bug 1155913 has been marked as a duplicate of this bug. *** |