Red Hat Bugzilla – Bug 1269504
[abrt] evolution-data-server: magazine_chain_pop_head(): evolution-calendar-factory-subprocess killed by SIGSEGV
Last modified: 2016-12-20 09:54:51 EST
Version-Release number of selected component:
cmdline: /usr/libexec/evolution-calendar-factory-subprocess --factory contacts --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx6685x2 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/6685/2
runlevel: N 5
Thread no. 1 (10 frames)
#0 magazine_chain_pop_head at gslice.c:539
#1 thread_memory_magazine1_alloc at gslice.c:842
#2 g_slice_alloc at gslice.c:998
#3 g_ptr_array_sized_new at garray.c:900
#4 g_ptr_array_new at garray.c:881
#5 g_main_context_new at gmain.c:649
#6 g_dbus_connection_send_message_with_reply_sync at gdbusconnection.c:2134
#7 g_dbus_connection_call_sync_internal at gdbusconnection.c:5930
#8 g_dbus_connection_call_with_unix_fd_list_sync at gdbusconnection.c:6276
#9 g_dbus_proxy_call_sync_internal at gdbusproxy.c:2852
Potential duplicate: bug 769523
Created attachment 1080647 [details]
Created attachment 1080648 [details]
Created attachment 1080649 [details]
Created attachment 1080650 [details]
Created attachment 1080651 [details]
Created attachment 1080652 [details]
Created attachment 1080653 [details]
Created attachment 1080654 [details]
Created attachment 1080655 [details]
Created attachment 1080656 [details]
Created attachment 1080657 [details]
Created attachment 1080658 [details]
Thanks for a bug report. It looks like some memory issue (memory corruption caused by the code) in the Birthdays & Anniversaries calendar backend.
Do you recall what you did before the crash, like for example enabling the calendar in the evolution, selecting a meeting invitation or similar actions within evolution or other Calendar application?
Sorry, I guess I just found the crash in ABRT window. I don't remember performing some exact steps.
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.