Bug 1277953

Summary: [abrt] gnome-calendar: icalarray_free(): gnome-calendar killed by SIGABRT
Product: [Fedora] Fedora Reporter: Nicolas Laplante <nicolas.laplante>
Component: gnome-calendarAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: ezwen-redhatbugzilla, fedora, gnome-sig, hfluz.jr, ignatenko, jack.gurulian, larryoleary, mcatanza, mcatanzaro+wrong-account-do-not-cc, peter
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e8e19b1b587794118c7654d726be3d770d0dfc78
Whiteboard: abrt_hash:9419a606f142c444e5d7b323eb69f7d1e43a97b6;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 16:38:22 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: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Nicolas Laplante 2015-11-04 12:16:07 UTC
Version-Release number of selected component:
gnome-calendar-3.18.1-1.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: icalarray_free
executable:     /usr/bin/gnome-calendar
global_pid:     5215
kernel:         4.2.3-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #6 icalarray_free at /usr/src/debug/libical-1.0.1/src/libical/icalarray.c:116
 #7 icaltimezone_expand_changes at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:522
 #8 icaltimezone_ensure_coverage at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:489
 #9 icaltimezone_get_utc_offset at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:852
 #10 icaltimezone_convert_time at /usr/src/debug/libical-1.0.1/src/libical/icaltimezone.c:807
 #11 icaltime_as_timet_with_zone at /usr/src/debug/libical-1.0.1/src/libical/icaltime.c:323
 #12 e_cal_recur_generate_instances_of_rule at e-cal-recur.c:716
 #13 e_cal_recur_generate_instances at e-cal-recur.c:640
 #14 generate_instances at e-cal-client.c:2670
 #15 e_cal_client_generate_instances_for_object_sync at e-cal-client.c:3327

Potential duplicate: bug 1220317

Comment 1 Nicolas Laplante 2015-11-04 12:16:12 UTC
Created attachment 1089603 [details]
File: backtrace

Comment 2 Nicolas Laplante 2015-11-04 12:16:13 UTC
Created attachment 1089604 [details]
File: cgroup

Comment 3 Nicolas Laplante 2015-11-04 12:16:15 UTC
Created attachment 1089605 [details]
File: core_backtrace

Comment 4 Nicolas Laplante 2015-11-04 12:16:16 UTC
Created attachment 1089606 [details]
File: dso_list

Comment 5 Nicolas Laplante 2015-11-04 12:16:17 UTC
Created attachment 1089607 [details]
File: environ

Comment 6 Nicolas Laplante 2015-11-04 12:16:18 UTC
Created attachment 1089608 [details]
File: limits

Comment 7 Nicolas Laplante 2015-11-04 12:16:19 UTC
Created attachment 1089609 [details]
File: maps

Comment 8 Nicolas Laplante 2015-11-04 12:16:21 UTC
Created attachment 1089610 [details]
File: mountinfo

Comment 9 Nicolas Laplante 2015-11-04 12:16:22 UTC
Created attachment 1089611 [details]
File: open_fds

Comment 10 Nicolas Laplante 2015-11-04 12:16:23 UTC
Created attachment 1089612 [details]
File: proc_pid_status

Comment 11 Igor Gnatenko 2016-09-14 08:06:06 UTC
I hope this has been resolved already, if not - please reopen bug.

Comment 12 Christian Stadelmann 2017-06-22 00:14:15 UTC
Not resolved, see bug #1463150 for a newer report.

Comment 13 Michael Catanzaro 2020-02-06 17:31:23 UTC
*** Bug 1463150 has been marked as a duplicate of this bug. ***

Comment 14 Michael Catanzaro 2020-02-06 17:31:35 UTC
*** Bug 1508459 has been marked as a duplicate of this bug. ***

Comment 15 Michael Catanzaro 2020-02-06 17:31:59 UTC
*** Bug 1754205 has been marked as a duplicate of this bug. ***

Comment 16 Michael Catanzaro 2020-02-06 17:32:01 UTC
*** Bug 1770576 has been marked as a duplicate of this bug. ***

Comment 17 Michael Catanzaro 2020-02-06 17:40:43 UTC
*** Bug 1772965 has been marked as a duplicate of this bug. ***

Comment 18 Ben Cotton 2020-11-03 14:57:16 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 19 Ben Cotton 2020-11-24 16:38:22 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.