Version-Release number of selected component: evolution-data-server-3.6.2-2.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: g_realloc executable: /usr/libexec/evolution-calendar-factory kernel: 3.6.10-4.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 g_realloc at gmem.c:224 #4 g_bsearch_array_grow at ../glib/gbsearcharray.h:213 #5 g_bsearch_array_insert at ../glib/gbsearcharray.h:242 #6 handler_list_ensure at gsignal.c:403 #7 handler_insert at gsignal.c:660 #8 g_signal_connect_data at gsignal.c:2449 #9 e_data_cal_init at e-data-cal.c:1733 #10 g_type_create_instance at gtype.c:1890 #11 g_object_constructor at gobject.c:1854 #13 g_object_new_valist at gobject.c:1835
Created attachment 695538 [details] File: backtrace
Created attachment 695539 [details] File: build_ids
Created attachment 695540 [details] File: cgroup
Created attachment 695541 [details] File: core_backtrace
Created attachment 695542 [details] File: dso_list
Created attachment 695543 [details] File: environ
Created attachment 695544 [details] File: limits
Created attachment 695545 [details] File: maps
Created attachment 695546 [details] File: open_fds
Created attachment 695547 [details] File: proc_pid_status
Created attachment 695548 [details] File: var_log_messages
From the bug summary: > I was writing over my home directory with a DejaDup backup around the time > this crash occurred; perhaps that was ... Thanks for a bug report. I think you are right, the background evolution processes were updating itself during the restore, which caused crash of one of them. I'm not sure how much it is currently fixable, but in any way, it's better to stop all evolution background processes before the restore, or even backup (though it might not be possible with gnome-shell, which seem to me restarts process if they close itself).
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.