Bug 1058530

Summary: [abrt] evolution-data-server: get_direction(): evolution-calendar-factory killed by SIGSEGV
Product: [Fedora] Fedora Reporter: jklein16
Component: evolution-data-serverAssignee: Milan Crha <mcrha>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fabiano, jklein16, mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4f66cb75c7c96730889321e4179daa3168c7cdfa
Whiteboard: abrt_hash:6efd34ee54a560908f898570cfd2c5142f699eb8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 14:48:30 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 jklein16 2014-01-28 01:17:49 UTC 
Version-Release number of selected component:
evolution-data-server-3.10.3-1.fc20

Additional info:
reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: get_direction
executable:     /usr/libexec/evolution-calendar-factory
kernel:         3.12.8-300.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 get_direction at e-cal-backend-intervaltree.c:84
 #1 binary_tree_insert at e-cal-backend-intervaltree.c:252
 #2 e_intervaltree_insert at e-cal-backend-intervaltree.c:511
 #3 add_component_to_intervaltree at e-cal-backend-file.c:653
 #4 add_component at e-cal-backend-file.c:740
 #5 scan_vcalendar at e-cal-backend-file.c:862
 #6 open_cal at e-cal-backend-file.c:1132
 #7 e_cal_backend_file_open at e-cal-backend-file.c:1400
 #8 e_cal_backend_sync_open at e-cal-backend-sync.c:49
 #9 cal_backend_open at e-cal-backend-sync.c:600
Comment 1 jklein16 2014-01-28 01:17:53 UTC 
Created attachment 856319 [details]
File: backtrace
Comment 2 jklein16 2014-01-28 01:17:54 UTC 
Created attachment 856320 [details]
File: cgroup
Comment 3 jklein16 2014-01-28 01:17:56 UTC 
Created attachment 856321 [details]
File: core_backtrace
Comment 4 jklein16 2014-01-28 01:17:58 UTC 
Created attachment 856322 [details]
File: dso_list
Comment 5 jklein16 2014-01-28 01:17:59 UTC 
Created attachment 856323 [details]
File: environ
Comment 6 jklein16 2014-01-28 01:18:01 UTC 
Created attachment 856324 [details]
File: exploitable
Comment 7 jklein16 2014-01-28 01:18:02 UTC 
Created attachment 856325 [details]
File: limits
Comment 8 jklein16 2014-01-28 01:18:04 UTC 
Created attachment 856326 [details]
File: maps
Comment 9 jklein16 2014-01-28 01:18:06 UTC 
Created attachment 856327 [details]
File: open_fds
Comment 10 jklein16 2014-01-28 01:18:07 UTC 
Created attachment 856328 [details]
File: proc_pid_status
Comment 11 jklein16 2014-01-28 01:18:09 UTC 
Created attachment 856329 [details]
File: var_log_messages
Comment 12 Milan Crha 2014-01-28 12:00:16 UTC 
Thanks for a bug report. I see from the backtrace that one of your local calendar had been opening, when the calendar factory crashed. Do you see this crash repeatedly, or it was just a one time crash? I'm wondering whether the crash depends on actual calendar content, because it seems to me it does.
Comment 13 Fedora Admin XMLRPC Client 2014-09-04 14:32:17 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 14 Fedora End Of Life 2015-05-29 10:42:25 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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'
of '20'.

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 20 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.
Comment 15 Fedora End Of Life 2015-06-29 14:48:30 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.
Comment 16 Red Hat Bugzilla 2023-09-14 02:02:44 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days