Red Hat Bugzilla – Bug 1283910
[abrt] evolution-data-server: g_hash_table_lookup(): evolution-source-registry killed by SIGSEGV
Last modified: 2016-12-20 11:07:47 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 g_hash_table_lookup at ghash.c:1152
#1 param_spec_ht_lookup at gparam.c:1003
#2 g_param_spec_pool_lookup at gparam.c:1076
#3 g_object_notify at gobject.c:1191
#4 source_idle_connection_status_change_cb at e-source.c:893
#9 dbus_server_run_server at e-dbus-server.c:232
#10 ffi_call_unix64 at ../src/x86/unix64.S:76
#11 ffi_call at ../src/x86/ffi64.c:525
#12 g_cclosure_marshal_generic_va at gclosure.c:1600
#13 _g_closure_invoke_va at gclosure.c:864
Created attachment 1097068 [details]
Created attachment 1097069 [details]
Created attachment 1097070 [details]
Created attachment 1097071 [details]
Created attachment 1097072 [details]
Created attachment 1097073 [details]
Created attachment 1097074 [details]
Created attachment 1097075 [details]
Created attachment 1097076 [details]
Created attachment 1097077 [details]
Created attachment 1097078 [details]
Created attachment 1097079 [details]
Thanks for a bug report. There seem to be no similar bug report filled upstream, neither here. I do not see much from the backtrace, just that one source (email account, calendar, addressbook...) connected to its destination (or disconnected) and it was about to notify others about it, but it failed due to accessing some memory it shouldn't (it can be like use-after-free or similar programming errors).
Do you have any hints on how to reproduce the crash, please?
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.