Created attachment 1289510 [details]
File: backtrace

Created attachment 1289511 [details]
File: cgroup

Created attachment 1289512 [details]
File: core_backtrace

Created attachment 1289513 [details]
File: cpuinfo

Created attachment 1289514 [details]
File: dso_list

Created attachment 1289515 [details]
File: environ

Created attachment 1289516 [details]
File: limits

Created attachment 1289517 [details]
File: maps

Created attachment 1289518 [details]
File: open_fds

Created attachment 1289520 [details]
File: proc_pid_status

Created attachment 1289522 [details]
File: var_log_messages

*** Bug 1464774 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I just plugged in an external screen, but that doesn't seem likely to be related to a gnome-calendar crash.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: icalarray_free
executable:     /usr/bin/gnome-calendar
journald_cursor: s=8a9e7701acfb4fcfbd314863a9a955a4;i=e0de2;b=9b3cf68b91e94b43ba4d5c99948a4263;m=264df890a;t=55423648d39fe;x=7ed99a0d91db163b
kernel:         4.11.9-300.fc26.x86_64
package:        gnome-calendar-3.24.3-1.fc26
reason:         gnome-calendar killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1471300 has been marked as a duplicate of this bug. ***

*** Bug 1472830 has been marked as a duplicate of this bug. ***

*** Bug 1473442 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I was not using gnome-calendar. The service crashed in the background.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: icalarray_free
executable:     /usr/bin/gnome-calendar
journald_cursor: s=ca44c691f28b4a3fa6affd95ab5151f5;i=aa1ab;b=7fb8229318334f2da9bbe95e11eea25a;m=7765771a4;t=5552ab0aa78b0;x=8410ddd371e44297
kernel:         4.11.11-300.fc26.x86_64
package:        gnome-calendar-3.24.3-1.fc26
reason:         gnome-calendar killed by signal 6
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1477100 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Just tried to start it.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: icalarray_free
executable:     /usr/bin/gnome-calendar
journald_cursor: s=35fb7d95f40844129607d66a5ba11f13;i=d9b7;b=7f0a32f5d039478e9099decd9d45567f;m=202aa881d;t=555c3dda5e91b;x=de6cf8610e278c6
kernel:         4.11.11-300.fc26.x86_64
package:        gnome-calendar-3.24.3-1.fc26
reason:         gnome-calendar killed by signal 6
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1478140 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

The crash occurred when I opened gnome-tweak-tool, but I don't know if there's a causal connection there.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: icalarray_free
executable:     /usr/bin/gnome-calendar
journald_cursor: s=1ae8309a3ebc4df197f4234c4fb41e5b;i=9378;b=16638f7c51904958af51dbce2ea19f1d;m=13aef8dfd3;t=557219a464ef0;x=651d355bd4ce7bcb
kernel:         4.12.5-300.fc26.x86_64
package:        gnome-calendar-3.24.3-1.fc26
reason:         gnome-calendar killed by signal 6
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1486013 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

Alert appeared after exiting mail client.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: icalarray_free
executable:     /usr/bin/gnome-calendar
journald_cursor: s=63d9f8c329544f1cbda8a56f502dd65b;i=605c;b=ebb907cccef4433a90118992fbf78eeb;m=a72bf32e0;t=558361dcf7400;x=a80c3471e42e46e5
kernel:         4.12.8-300.fc26.x86_64
package:        gnome-calendar-3.24.3-1.fc26
reason:         gnome-calendar killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

*** Bug 1492337 has been marked as a duplicate of this bug. ***

*** Bug 1492850 has been marked as a duplicate of this bug. ***

*** Bug 1494279 has been marked as a duplicate of this bug. ***

*** Bug 1495093 has been marked as a duplicate of this bug. ***

*** Bug 1497644 has been marked as a duplicate of this bug. ***

*** Bug 1545938 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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.

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.

*** This bug has been marked as a duplicate of bug 1277953 ***