Bug 909605

Summary: [abrt] evolution-data-server-3.6.2-2.fc18: g_realloc: Process /usr/libexec/evolution-calendar-factory was killed by signal 11 (SIGSEGV) I was writing over my home directory with a DejaDup backup around the time this crash occurred; perhaps that was ...
Product: [Fedora] Fedora Reporter: Michael Catanzaro <mcatanzaro>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5b892a2e097bd05f893ddd4a2c34713c32d96763
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 19:03:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: build_ids
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Michael Catanzaro 2013-02-09 19:22:26 UTC 
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
Comment 1 Michael Catanzaro 2013-02-09 19:22:29 UTC 
Created attachment 695538 [details]
File: backtrace
Comment 2 Michael Catanzaro 2013-02-09 19:22:30 UTC 
Created attachment 695539 [details]
File: build_ids
Comment 3 Michael Catanzaro 2013-02-09 19:22:32 UTC 
Created attachment 695540 [details]
File: cgroup
Comment 4 Michael Catanzaro 2013-02-09 19:22:33 UTC 
Created attachment 695541 [details]
File: core_backtrace
Comment 5 Michael Catanzaro 2013-02-09 19:22:35 UTC 
Created attachment 695542 [details]
File: dso_list
Comment 6 Michael Catanzaro 2013-02-09 19:22:36 UTC 
Created attachment 695543 [details]
File: environ
Comment 7 Michael Catanzaro 2013-02-09 19:22:38 UTC 
Created attachment 695544 [details]
File: limits
Comment 8 Michael Catanzaro 2013-02-09 19:22:40 UTC 
Created attachment 695545 [details]
File: maps
Comment 9 Michael Catanzaro 2013-02-09 19:22:41 UTC 
Created attachment 695546 [details]
File: open_fds
Comment 10 Michael Catanzaro 2013-02-09 19:22:43 UTC 
Created attachment 695547 [details]
File: proc_pid_status
Comment 11 Michael Catanzaro 2013-02-09 19:22:45 UTC 
Created attachment 695548 [details]
File: var_log_messages
Comment 12 Milan Crha 2013-02-11 10:45:20 UTC 
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).
Comment 13 Fedora End Of Life 2013-12-21 11:17:23 UTC 
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.
Comment 14 Fedora End Of Life 2014-02-05 19:03:55 UTC 
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.