Red Hat Bugzilla – Bug 975112
[abrt] evolution-3.8.3-1.fc19: dconf_engine_change_notify: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-17 10:36:37 EST
Description of problem:
I clicked on evolution
it opened for a couple seconds and disapeared.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 dconf_engine_change_notify at dconfsettingsbackend.c:242
#1 dconf_engine_emit_changes at dconf-engine.c:871
#2 dconf_engine_change_fast at dconf-engine.c:1084
#3 dconf_settings_backend_write at dconfsettingsbackend.c:79
#4 g_settings_backend_write at gsettingsbackend.c:778
#5 g_settings_write_to_backend at gsettings.c:1025
#6 g_settings_binding_property_changed at gsettings.c:2473
#12 g_object_notify_queue_thaw at gobject.c:292
#13 g_object_thaw_notify at gobject.c:1270
#14 gtk_paned_calc_position at gtkpaned.c:2134
Created attachment 762088 [details]
Created attachment 762089 [details]
Created attachment 762090 [details]
Created attachment 762091 [details]
Created attachment 762092 [details]
Created attachment 762093 [details]
Created attachment 762094 [details]
Created attachment 762095 [details]
Created attachment 762096 [details]
Created attachment 762097 [details]
Thanks for a bug report. I see this crashes deep in DConf code, in evolution's main thread. I do not expect anything being wrong with associated widgets, thus I guess this has something to do with DCong itself, though it didn't change for the past three months. Maybe something with GLib?
Do you see this after some update? If so, is it crashing each start? Will it help to downgrade updated packages? I would start with glib2, but I've no idea whether it'll help.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.