Bug 1427995

Summary: [abrt] gnome-calendar: icalarray_free(): gnome-calendar killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Mark Tinberg <mtinberg>
Component: gnome-calendarAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: gnome-sig, ignatenko, sascha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/bb4570e6754f748023295c72c1e7435038d0d3ac
Whiteboard: abrt_hash:9419a606f142c444e5d7b323eb69f7d1e43a97b6;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-12 10:03:03 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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Mark Tinberg 2017-03-01 16:35:00 UTC 
Description of problem:
I see this ABRT right when I log in, I have Evolution set up to start on login and it has accounts on Gmail and O365

Version-Release number of selected component:
gnome-calendar-3.22.2-1.fc25

Additional info:
reporter:       libreport-2.8.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: icalarray_free
executable:     /usr/bin/gnome-calendar
global_pid:     4045
kernel:         4.9.11-200.fc25.x86_64
pkg_fingerprint: 4089 D8F2 FDB1 9C98
pkg_vendor:     Fedora Project
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 icalarray_free at /usr/src/debug/libical-2.0.0/src/libical/icalarray.c:109
 #1 icaltimezone_expand_changes at /usr/src/debug/libical-2.0.0/src/libical/icaltimezone.c:478
 #2 icaltimezone_ensure_coverage at /usr/src/debug/libical-2.0.0/src/libical/icaltimezone.c:450
 #3 icaltimezone_get_utc_offset at /usr/src/debug/libical-2.0.0/src/libical/icaltimezone.c:782
 #4 icaltimezone_convert_time at /usr/src/debug/libical-2.0.0/src/libical/icaltimezone.c:743
 #5 icaltime_convert_to_zone at /usr/src/debug/libical-2.0.0/src/libical/icaltime.c:1027
 #6 icaltime_compare at /usr/src/debug/libical-2.0.0/src/libical/icaltime.c:782
 #7 e_timetype_compare_without_date at e-cal-recur.c:70
 #8 intersects_interval at e-cal-recur.c:294
 #10 e_cal_recur_generate_instances_sync at e-cal-recur.c:594

Potential duplicate: bug 1277953
Comment 1 Mark Tinberg 2017-03-01 16:35:05 UTC 
Created attachment 1258812 [details]
File: backtrace
Comment 2 Mark Tinberg 2017-03-01 16:35:06 UTC 
Created attachment 1258813 [details]
File: cgroup
Comment 3 Mark Tinberg 2017-03-01 16:35:07 UTC 
Created attachment 1258814 [details]
File: core_backtrace
Comment 4 Mark Tinberg 2017-03-01 16:35:09 UTC 
Created attachment 1258815 [details]
File: dso_list
Comment 5 Mark Tinberg 2017-03-01 16:35:09 UTC 
Created attachment 1258816 [details]
File: environ
Comment 6 Mark Tinberg 2017-03-01 16:35:10 UTC 
Created attachment 1258817 [details]
File: exploitable
Comment 7 Mark Tinberg 2017-03-01 16:35:11 UTC 
Created attachment 1258818 [details]
File: limits
Comment 8 Mark Tinberg 2017-03-01 16:35:13 UTC 
Created attachment 1258819 [details]
File: maps
Comment 9 Mark Tinberg 2017-03-01 16:35:14 UTC 
Created attachment 1258820 [details]
File: mountinfo
Comment 10 Mark Tinberg 2017-03-01 16:35:15 UTC 
Created attachment 1258821 [details]
File: namespaces
Comment 11 Mark Tinberg 2017-03-01 16:35:16 UTC 
Created attachment 1258822 [details]
File: open_fds
Comment 12 Mark Tinberg 2017-03-01 16:35:17 UTC 
Created attachment 1258823 [details]
File: proc_pid_status
Comment 13 Mark Tinberg 2017-03-01 16:35:19 UTC 
Created attachment 1258824 [details]
File: var_log_messages
Comment 14 Fedora End Of Life 2017-11-16 14:30:21 UTC 
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 2017-12-12 10:03:03 UTC 
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.