Bug 1437669
| Summary: | [abrt] Crash under on_connection_disconnected() | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vladimir Benes <vbenes> | |
| Component: | glib2 | Assignee: | Colin Walters <walters> | |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 7.4 | CC: | mcrha, ovasik, tpelka | |
| Target Milestone: | rc | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| URL: | http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/de496f0d21defd3bc43f4092694c8895ed12ee74/ | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1498975 (view as bug list) | Environment: | ||
| Last Closed: | 2017-08-01 12:28:09 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: | ||||
| Bug Blocks: | 1498975 | |||
|
Description
Vladimir Benes
2017-03-30 20:48:03 UTC
Thanks for a bug report. This is similar as Fedora bug #1172229. It's crashing in a dconf_gdbus_worker_thread(), nothing eds has control of. As it's also under glib's on_connection_disconnected(). A very wild guess is: https://bugzilla.gnome.org/show_bug.cgi?id=703045 with a relation to https://bugzilla.gnome.org/show_bug.cgi?id=748263 No interest from the glib side upstream, unfortunately. I may try to look at this...yes, those bugs w/patches have been left in limbo far too long. But what's the justification for the Regression tag? This was recently fixed upstream, and is an easy low-risk backport. 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-2017:2100 |