Bug 1109600

Summary: [abrt] evolution-data-server: g_child_source_remove_internal(): evolution-calendar-factory killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Jan Vlug <jan.public>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fabiano, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/97f14863ced1301d972871b018a8967a811605f0
Whiteboard: abrt_hash:fbcc5d16578478cc9e0ef4cf0f75b2c71a6d89dc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-16 08:49:23 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: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jan Vlug 2014-06-15 19:59:19 UTC 
Version-Release number of selected component:
evolution-data-server-3.10.4-3.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: g_child_source_remove_internal
executable:     /usr/libexec/evolution-calendar-factory
kernel:         3.14.4-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            500

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 g_child_source_remove_internal at gmain.c:1448
 #1 g_source_destroy_internal at gmain.c:1227
 #6 gdbus_shared_thread_func at gdbusprivate.c:278
 #7 g_thread_proxy at gthread.c:798
Comment 1 Jan Vlug 2014-06-15 19:59:24 UTC 
Created attachment 908937 [details]
File: backtrace
Comment 2 Jan Vlug 2014-06-15 19:59:26 UTC 
Created attachment 908938 [details]
File: cgroup
Comment 3 Jan Vlug 2014-06-15 19:59:28 UTC 
Created attachment 908939 [details]
File: core_backtrace
Comment 4 Jan Vlug 2014-06-15 19:59:31 UTC 
Created attachment 908940 [details]
File: dso_list
Comment 5 Jan Vlug 2014-06-15 19:59:32 UTC 
Created attachment 908941 [details]
File: environ
Comment 6 Jan Vlug 2014-06-15 19:59:34 UTC 
Created attachment 908942 [details]
File: exploitable
Comment 7 Jan Vlug 2014-06-15 19:59:36 UTC 
Created attachment 908943 [details]
File: limits
Comment 8 Jan Vlug 2014-06-15 19:59:38 UTC 
Created attachment 908944 [details]
File: maps
Comment 9 Jan Vlug 2014-06-15 19:59:40 UTC 
Created attachment 908945 [details]
File: open_fds
Comment 10 Jan Vlug 2014-06-15 19:59:41 UTC 
Created attachment 908946 [details]
File: proc_pid_status
Comment 11 Jan Vlug 2014-06-15 19:59:44 UTC 
Created attachment 908947 [details]
File: var_log_messages
Comment 12 Milan Crha 2014-06-16 08:49:23 UTC 
Thanks for a bug report. I guess this crashed due to some memory corruption, like when some part of the code writes to an already freed memory. I guess so due to the place of the crash. I guess this just happened in the background, probably after some periodic update of one of your configured calendars, even it is not visible from the backtrace at all.