Bug 970938
| Summary: | [abrt] glib2-2.26.0-2.el6: g_settings_schema_new: Process /usr/bin/gsettings was killed by signal 6 (SIGABRT) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | David Jaša <djasa> | ||||
| Component: | glib2 | Assignee: | Colin Walters <walters> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.4 | CC: | mbarnes, mcrha, tpelka | ||||
| Target Milestone: | beta | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:032796346c3c7969157d51b54b66d885829953fc | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-12-06 11:46:24 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: | |||||||
| Attachments: |
|
||||||
|
Description
David Jaša
2013-06-05 09:31:06 UTC
There are several occurrences of these crashes per _hour_, so I'm raising severity to get this fixed asap. CCing also Evolution people who did the first build of 2.26 stuff for RHEL6. Could you provide full backtrace and console output, please? From the command line:
> gsettings get org.gnome.system.proxy mode
I would guess that you do not have installed 'org.gnome.system.proxy' scheme, or it doesn't contain 'mode' key. Such errors are usually written on console.
Created attachment 760930 [details]
full bt by abrt
$ gsettings get org.gnome.system.proxy mode GLib-GIO-ERROR **: Settings schema 'org.gnome.system.proxy' is not installed aborting... Neúspěšně ukončen (SIGABRT) (core dumped [obraz paměti uložen]) this gsettings command results in the same backtrace. OK, it makes sense, GSettings is a bit dumb and aborts on situation when there is no scheme for a key. The question is: where did you find this command and/or key, please? The comment #0 shows you (or a script?) run such command, and the abort is a way of GSettings to "report" error, thus it's expected it'll end this way. I have no idea what might call gsettings but I noticed that: 1) If I'm on corporate network, the crashes do not occur 2) the crashes are much more likely to occur if I have evo calendar running - isn't there some logic that asks for proxy setting if connection can't be established right away? anyway, CLI commands shouldn't abort in normal circumstances - where trying to access undefined setting belong. Non-zero exit code is the right thing to do. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/ |