Red Hat Bugzilla – Bug 1255482
[abrt] evolution-data-server: g_type_check_instance_is_fundamentally_a(): evolution-calendar-factory killed by SIGSEGV
Last modified: 2016-12-20 09:26:44 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (7 frames)
#0 g_type_check_instance_is_fundamentally_a at gtype.c:4028
#1 g_object_ref at gobject.c:3040
#2 data_factory_connections_add at e-data-factory.c:512
#3 data_factory_call_subprocess_backend_create_sync at e-data-factory.c:544
#4 data_factory_spawn_subprocess_backend at e-data-factory.c:1230
#5 data_factory_spawn_subprocess_backend_in_thread at e-data-factory.c:1337
#6 g_thread_proxy at gthread.c:764
Created attachment 1065337 [details]
Created attachment 1065338 [details]
Created attachment 1065339 [details]
Created attachment 1065340 [details]
Created attachment 1065341 [details]
Created attachment 1065342 [details]
Created attachment 1065343 [details]
Created attachment 1065344 [details]
Created attachment 1065345 [details]
Created attachment 1065346 [details]
Created attachment 1065347 [details]
Created attachment 1065348 [details]
Thanks for a bug rpeort. The backtrace shows that the crash happened when the On This Computer/Personal memo list had been opened, though it seems like some memory corruption got involved and the code crashed. As these things can be related to some use-after-free issues, then the memo list opening might not have any direct connection to the place of the real issue.
Do you have any idea what could happen before 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.