Bug 1561868 - [abrt] gnome-calendar: gtk_image_reset(): gnome-calendar killed by SIGSEGV
Summary: [abrt] gnome-calendar: gtk_image_reset(): gnome-calendar killed by SIGSEGV
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-calendar
Version: 30
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Igor Raits
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:7986938efbf9c20e1d29bbeaf16...
: 1564560 1568533 1572443 1573469 1573525 1573710 1573724 1574641 1575277 1576243 1576900 1582536 1586349 1590011 1609498 1621229 1622307 1630767 1630852 1692389 1695221 1695277 1698120 1704903 1705323 1706197 1706383 1706643 1706977 1707771 1710651 1710705 1714097 1716121 1716435 1718550 1723913 1724070 1724172 1726647 1727978 1729050 1729624 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-29 05:21 UTC by Dawid Zamirski
Modified: 2019-09-03 12:02 UTC (History)
58 users (show)

Fixed In Version: gnome-calendar-3.32.2-5.fc30
Clone Of:
Environment:
Last Closed: 2019-07-26 00:59:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (45.25 KB, text/plain)
2018-03-29 05:21 UTC, Dawid Zamirski 		no flags Details
File: cgroup (365 bytes, text/plain)
2018-03-29 05:21 UTC, Dawid Zamirski 		no flags Details
File: core_backtrace (20.13 KB, text/plain)
2018-03-29 05:21 UTC, Dawid Zamirski 		no flags Details
File: cpuinfo (1.44 KB, text/plain)
2018-03-29 05:21 UTC, Dawid Zamirski 		no flags Details
File: dso_list (22.05 KB, text/plain)
2018-03-29 05:21 UTC, Dawid Zamirski 		no flags Details
File: environ (1.66 KB, text/plain)
2018-03-29 05:21 UTC, Dawid Zamirski 		no flags Details
File: exploitable (82 bytes, text/plain)
2018-03-29 05:21 UTC, Dawid Zamirski 		no flags Details
File: limits (1.29 KB, text/plain)
2018-03-29 05:21 UTC, Dawid Zamirski 		no flags Details
File: maps (103.98 KB, text/plain)
2018-03-29 05:22 UTC, Dawid Zamirski 		no flags Details
File: mountinfo (4.04 KB, text/plain)
2018-03-29 05:22 UTC, Dawid Zamirski 		no flags Details
File: open_fds (1.42 KB, text/plain)
2018-03-29 05:22 UTC, Dawid Zamirski 		no flags Details
File: proc_pid_status (1.27 KB, text/plain)
2018-03-29 05:22 UTC, Dawid Zamirski 		no flags Details
File: var_log_messages (11.71 KB, text/plain)
2018-03-29 05:22 UTC, Dawid Zamirski 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME/gnome-calendar/issues/299 0 None None None 2019-07-03 15:15:59 UTC

Description Dawid Zamirski 2018-03-29 05:21:47 UTC 
Version-Release number of selected component:
gnome-calendar-3.28.0-1.fc28

Additional info:
reporter:       libreport-2.9.4
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=8ec806abc0b94ae5bb5e4a205ab97bc5;i=3050;b=f8cff3d46a884f08ac02aae1594d9c39;m=705f6b2d;t=56885e85f03af;x=5f594dabcaa1f23
kernel:         4.16.0-0.rc7.git0.1.fc28.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 gtk_image_reset at gtkimage.c:1909
 #1 gtk_image_clear at gtkimage.c:1909
 #2 update_weather at ../src/views/gcal-year-view.c:2113
 #8 gcal_weather_service_stop at ../src/weather/gcal-weather-service.c:1175
 #9 gcal_window_finalize at ../src/gcal-window.c:1232
 #11 gtk_main_do_event at gtkmain.c:1832
 #12 send_delete_event at gtkwindow.c:1324
 #18 g_main_context_iteration at gmain.c:3964
 #19 g_application_run at gapplication.c:2482
Comment 1 Dawid Zamirski 2018-03-29 05:21:51 UTC 
Created attachment 1414525 [details]
File: backtrace
Comment 2 Dawid Zamirski 2018-03-29 05:21:53 UTC 
Created attachment 1414526 [details]
File: cgroup
Comment 3 Dawid Zamirski 2018-03-29 05:21:54 UTC 
Created attachment 1414527 [details]
File: core_backtrace
Comment 4 Dawid Zamirski 2018-03-29 05:21:55 UTC 
Created attachment 1414528 [details]
File: cpuinfo
Comment 5 Dawid Zamirski 2018-03-29 05:21:56 UTC 
Created attachment 1414529 [details]
File: dso_list
Comment 6 Dawid Zamirski 2018-03-29 05:21:57 UTC 
Created attachment 1414530 [details]
File: environ
Comment 7 Dawid Zamirski 2018-03-29 05:21:58 UTC 
Created attachment 1414531 [details]
File: exploitable
Comment 8 Dawid Zamirski 2018-03-29 05:21:59 UTC 
Created attachment 1414532 [details]
File: limits
Comment 9 Dawid Zamirski 2018-03-29 05:22:02 UTC 
Created attachment 1414533 [details]
File: maps
Comment 10 Dawid Zamirski 2018-03-29 05:22:03 UTC 
Created attachment 1414534 [details]
File: mountinfo
Comment 11 Dawid Zamirski 2018-03-29 05:22:04 UTC 
Created attachment 1414535 [details]
File: open_fds
Comment 12 Dawid Zamirski 2018-03-29 05:22:05 UTC 
Created attachment 1414536 [details]
File: proc_pid_status
Comment 13 Dawid Zamirski 2018-03-29 05:22:06 UTC 
Created attachment 1414537 [details]
File: var_log_messages
Comment 14 Florian Alber 2018-04-04 20:29:07 UTC 
Similar problem has been detected:

Hi,

I tried to set up the account synchronization of my google calendar, but it has crashed.

Greetings,
albflo

reporter:       libreport-2.9.4
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=1b6dcbba0b804a498326410df564bb35;i=afc6;b=6db85b4dce554bae99b880ba29629ead;m=12db1529a;t=5690b7a9171ed;x=fcf7f62a621834db
kernel:         4.16.0-0.rc7.git0.1.fc28.x86_64
package:        gnome-calendar-3.28.0-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 15 lray+redhatbugzilla 2018-04-05 21:27:03 UTC 
Similar problem has been detected:

switch from weekly to monthly view, exiting afterwards.

reporter:       libreport-2.9.4
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=9261104b255640eaa6741a4c23a9759b;i=186c19;b=876fa27c6fcb446f9e66f6e383a3c35b;m=46b266c37;t=5692077a4ffc6;x=6f42fd8bb68d6a27
kernel:         4.16.0-300.fc28.x86_64
package:        gnome-calendar-3.28.0-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 16 Brandon Bennett 2018-04-06 15:36:26 UTC 
*** Bug 1564560 has been marked as a duplicate of this bug. ***
Comment 17 Lukas Ruzicka 2018-04-11 09:39:23 UTC 
Similar problem has been detected:

After I added and deleted some events from the calendar, I clicked on the cross to close the application. It closed, but it also reported this error.

reporter:       libreport-2.9.4
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=602ca6fd81a24d92a06da388c063703a;i=174b;b=017f5443ff0b425e9bbbfd6fefdb490b;m=d27170c8;t=5698f31de7224;x=a30522b276c973
kernel:         4.16.1-300.fc28.x86_64
package:        gnome-calendar-3.28.0-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 18 Ankur Sinha (FranciscoD) 2018-04-11 12:54:45 UTC 
Similar problem has been detected:

Crashed on exit.

reporter:       libreport-2.9.4
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=14326aefa44342edb1e41e545a13dfd1;i=4df77c;b=af96f42f2659488facabd8de4571623b;m=2acaaceade;t=56992117640b8;x=f9b9384b0f60fc7d
kernel:         4.16.0-0.rc7.git0.1.fc28.x86_64
package:        gnome-calendar-3.28.0-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 19 Hayden 2018-04-17 17:16:29 UTC 
*** Bug 1568533 has been marked as a duplicate of this bug. ***
Comment 20 Leslie Satenstein 2018-04-18 14:48:39 UTC 
Gnome-Calendar is crashing on exit from autostart.

Activities.
Enter a transaction for tomorrow or yesterday.

exit calendar.

Crash
Comment 21 Ed Marshall 2018-04-18 23:56:14 UTC 
Similar problem has been detected:

Closed gnome-calendar.

reporter:       libreport-2.9.4
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=d56bd705b9a74a56b1aed2f6235d7e63;i=3c7f;b=d4ae1f06a56e482693c76907233f230d;m=4c04f079;t=56a27f8fadfc6;x=96397566718bf8f0
kernel:         4.16.2-300.fc28.x86_64
package:        gnome-calendar-3.28.1-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 22 Carl Stork 2018-04-27 02:55:40 UTC 
*** Bug 1572443 has been marked as a duplicate of this bug. ***
Comment 23 François Perriot 2018-04-29 13:06:35 UTC 
Similar problem has been detected:

I open gnome-calendar. I displayed an event. Then I exited.
Soone after I got the abrt notification.

reporter:       libreport-2.9.4
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=54418eeb5d894ca59b8c3a1109032007;i=4ad47;b=2e47160027dd489c9796859645eea244;m=31bfaedd;t=56afc415b79b7;x=ad0f1083a5eef01f
kernel:         4.16.4-300.fc28.x86_64
package:        gnome-calendar-3.28.1-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 24 lray+redhatbugzilla 2018-04-29 13:13:40 UTC 
Similar problem has been detected:

Ical import using nautilus context-link

reporter:       libreport-2.9.4
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=437e9a78c8934706bdf591280b94cf11;i=4258f;b=61dac325e9d0497293c0532abc85be5a;m=1f8593eb6;t=56afa3f769ad7;x=bb883a0322911dce
kernel:         4.16.3-301.fc28.x86_64
package:        gnome-calendar-3.28.1-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 25 Andrew Gunnerson 2018-04-30 11:56:21 UTC 
Similar problem has been detected:

I just opened gnome-calendar and closed it about 15 seconds later without interacting with the application.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=19050200825a4edaa4d44592a027d40b;i=1e357;b=465c9030401143a48f44eddc7f005bcf;m=160a63032;t=56b004f3f1c1e;x=2b798ba123853c0b
kernel:         4.16.4-300.fc28.x86_64
package:        gnome-calendar-3.28.1-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 26 Kyriakos Fytrakis 2018-05-01 11:40:16 UTC 
*** Bug 1573469 has been marked as a duplicate of this bug. ***
Comment 27 dorofieiev.d 2018-05-01 15:31:07 UTC 
*** Bug 1573525 has been marked as a duplicate of this bug. ***
Comment 28 Fernando 2018-05-02 06:01:31 UTC 
*** Bug 1573710 has been marked as a duplicate of this bug. ***
Comment 29 a.preis1989 2018-05-02 07:02:31 UTC 
*** Bug 1573724 has been marked as a duplicate of this bug. ***
Comment 30 Kyriakos Fytrakis 2018-05-02 09:34:40 UTC 
Similar problem has been detected:

I was trying to add a calendar from a web link. I did not succeed. The error encountered after closing the application. 

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=cd0d39ae453840edbe190f2822bb0976;i=13db2;b=b6ec73685ebf4958b9c81c345b7a9c0b;m=17223cb18;t=56b35b1e6e6e4;x=63617feaa5a42f77
kernel:         4.16.5-300.fc28.x86_64
package:        gnome-calendar-3.28.1-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 31 Ryan Gillette 2018-05-03 18:30:40 UTC 
*** Bug 1574641 has been marked as a duplicate of this bug. ***
Comment 32 Alessio 2018-05-03 21:37:50 UTC 
Similar problem has been detected:

Don't know.
After I closed gnome calendar, I got this report.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=e0e5d17b04944a0189b64c01113ba2fa;i=19e82;b=ea36b35ed4bf4e96bb18962aa3f414ef;m=165e81f70;t=56b53f0f3eeb7;x=47bd66ce97ca7b3e
kernel:         4.16.6-300.fc28.x86_64
package:        gnome-calendar-3.28.1-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 33 Gheorghi Isac 2018-05-04 13:01:40 UTC 
Similar problem has been detected:

I opened Calculator app, and after 1 min I closed it.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=33c3d68ddabe4fab9ed3eef1b95ee1cb;i=17a3f;b=9573a485eb4a4a04baa0b6d5ef8d1861;m=a56b81d2;t=56b60de629aaa;x=90c6cc7caec7fc30
kernel:         4.16.5-300.fc28.x86_64
package:        gnome-calendar-3.28.1-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 34 Richard Ruhland 2018-05-05 15:47:53 UTC 
*** Bug 1575277 has been marked as a duplicate of this bug. ***
Comment 35 guiofcancer 2018-05-09 06:50:11 UTC 
*** Bug 1576243 has been marked as a duplicate of this bug. ***
Comment 36 lacesz 2018-05-10 16:21:31 UTC 
*** Bug 1576900 has been marked as a duplicate of this bug. ***
Comment 37 Sajith Thrimavithana 2018-05-15 17:58:13 UTC 
Similar problem has been detected:

When simply navigating day to day in the calander. 

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=7a5d5729bece4dc6aa3c6f269cd6fe8e;i=3634;b=c88d34dfcb674c36b07d7077a013b886;m=8a9e1029;t=56c4231f0c0be;x=427aad440f0f9972
kernel:         4.16.3-301.fc28.x86_64
package:        gnome-calendar-3.28.1-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 38 gudbugsarwontfix 2018-05-25 13:59:52 UTC 
*** Bug 1582536 has been marked as a duplicate of this bug. ***
Comment 39 sukhamay ganguly 2018-06-06 04:12:53 UTC 
*** Bug 1586349 has been marked as a duplicate of this bug. ***
Comment 40 Fernando 2018-06-11 20:56:02 UTC 
*** Bug 1590011 has been marked as a duplicate of this bug. ***
Comment 41 anuragsoni.13 2018-07-28 16:05:40 UTC 
*** Bug 1609498 has been marked as a duplicate of this bug. ***
Comment 42 Igor Raits 2018-08-02 15:32:33 UTC 
Please test with latest updates and reopen if still reproducible.
Comment 43 Elton 2018-08-23 14:26:44 UTC 
*** Bug 1621229 has been marked as a duplicate of this bug. ***
Comment 44 Christian Zieske 2018-08-25 16:54:04 UTC 
*** Bug 1622307 has been marked as a duplicate of this bug. ***
Comment 45 Christian Stadelmann 2018-09-09 15:41:26 UTC 
Similar problem has been detected:

Every time I close gnome-calendar, it crashes.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=ef01adf0829f42b2896c9a5bb27a1bac;i=370407;b=fcf8f2c9dd584b72b95984d61395a9db;m=245287aa80;t=575720a5f01ef;x=acd6f76dc095897f
kernel:         4.17.19-200.fc28.x86_64
package:        gnome-calendar-3.28.2-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
Comment 46 Christian Stadelmann 2018-09-09 15:42:38 UTC 
Please reopen this bug report. The crash is still present with gnome-calendar-3.28.2-1.fc28.x86_64.
Comment 47 Basem Taha 2018-09-19 12:40:21 UTC 
*** Bug 1630852 has been marked as a duplicate of this bug. ***
Comment 48 Jan Vlug 2018-10-12 08:26:34 UTC 
Similar problem has been detected:

Trying to unselect a Nextcloud calendar.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=f8bee9379dcb407f80ebbf8eca34b3d0;i=32eae;b=e35717e120bd4792a58154fe761fd7d5;m=9dd04e21;t=57803319bb392;x=edbe8fcdf4ad6888
kernel:         4.18.12-200.fc28.x86_64
package:        gnome-calendar-3.28.2-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 49 rugk 2018-10-28 21:00:20 UTC 
Similar problem has been detected:

Tried to delete a local calender. i just had deleted the calendar ics file before.

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=462593842ff340cb8a33c39f0bfd0134;i=294d30;b=76b027a48c12467091f215aeda0cc22f;m=1068f3ec1;t=5794f56d7f3ae;x=2dbfd8266b1acce
kernel:         4.18.16-200.fc28.x86_64
package:        gnome-calendar-3.28.2-1.fc28
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 50 Tim Waugh 2018-10-30 09:53:12 UTC 
I saw this with gnome-calendar-3.28.2-1.fc28.x86_64 today.
Comment 51 Ben Cotton 2019-05-02 20:32:31 UTC 
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 52 Ben Cotton 2019-05-28 23:04:49 UTC 
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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 53 Michael Catanzaro 2019-07-03 15:08:55 UTC 
*** Bug 1710651 has been marked as a duplicate of this bug. ***
Comment 54 Michael Catanzaro 2019-07-03 15:09:00 UTC 
*** Bug 1710705 has been marked as a duplicate of this bug. ***
Comment 55 Michael Catanzaro 2019-07-03 15:09:25 UTC 
*** Bug 1726647 has been marked as a duplicate of this bug. ***
Comment 56 Michael Catanzaro 2019-07-03 15:09:35 UTC 
*** Bug 1724172 has been marked as a duplicate of this bug. ***
Comment 57 Michael Catanzaro 2019-07-03 15:10:23 UTC 
*** Bug 1714097 has been marked as a duplicate of this bug. ***
Comment 58 Michael Catanzaro 2019-07-03 15:10:27 UTC 
*** Bug 1716121 has been marked as a duplicate of this bug. ***
Comment 59 Michael Catanzaro 2019-07-03 15:10:30 UTC 
*** Bug 1716435 has been marked as a duplicate of this bug. ***
Comment 60 Michael Catanzaro 2019-07-03 15:10:33 UTC 
*** Bug 1718550 has been marked as a duplicate of this bug. ***
Comment 61 Michael Catanzaro 2019-07-03 15:10:37 UTC 
*** Bug 1723913 has been marked as a duplicate of this bug. ***
Comment 62 Michael Catanzaro 2019-07-03 15:10:40 UTC 
*** Bug 1724070 has been marked as a duplicate of this bug. ***
Comment 63 Michael Catanzaro 2019-07-03 15:11:12 UTC 
*** Bug 1706977 has been marked as a duplicate of this bug. ***
Comment 64 Michael Catanzaro 2019-07-03 15:11:47 UTC 
*** Bug 1706643 has been marked as a duplicate of this bug. ***
Comment 65 Michael Catanzaro 2019-07-03 15:12:23 UTC 
*** Bug 1698120 has been marked as a duplicate of this bug. ***
Comment 66 Michael Catanzaro 2019-07-03 15:12:27 UTC 
*** Bug 1704903 has been marked as a duplicate of this bug. ***
Comment 67 Michael Catanzaro 2019-07-03 15:12:32 UTC 
*** Bug 1705323 has been marked as a duplicate of this bug. ***
Comment 68 Michael Catanzaro 2019-07-03 15:12:39 UTC 
*** Bug 1706197 has been marked as a duplicate of this bug. ***
Comment 69 Michael Catanzaro 2019-07-03 15:12:52 UTC 
*** Bug 1706383 has been marked as a duplicate of this bug. ***
Comment 70 Michael Catanzaro 2019-07-03 15:12:57 UTC 
*** Bug 1707771 has been marked as a duplicate of this bug. ***
Comment 71 Michael Catanzaro 2019-07-03 15:14:14 UTC 
*** Bug 1695277 has been marked as a duplicate of this bug. ***
Comment 72 Michael Catanzaro 2019-07-03 15:14:21 UTC 
*** Bug 1695221 has been marked as a duplicate of this bug. ***
Comment 73 Michael Catanzaro 2019-07-03 15:14:27 UTC 
*** Bug 1692389 has been marked as a duplicate of this bug. ***
Comment 74 Michael Catanzaro 2019-07-03 15:15:22 UTC 
*** Bug 1630767 has been marked as a duplicate of this bug. ***
Comment 75 Gheorghi Isac 2019-07-10 10:06:42 UTC 
Similar problem has been detected:

I just clicked "Synchronize" and the application closed.

reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=ec381fd655384be485b894e3c98b18f9;i=a585;b=385cfc02b4be402a83a1f674064371ef;m=16dd6230d1;t=58d50a378b0a2;x=ebebc08033aa2b2
kernel:         5.1.16-300.fc30.x86_64
package:        gnome-calendar-3.32.2-1.fc30
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 76 Yajo 2019-07-17 07:50:48 UTC 
Similar problem has been detected:

Changed event name in a single occurrence of a repeated event.

reporter:       libreport-2.10.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=8d58cd64f672453bb07027a88bae98b7;i=21926;b=478cff891fe5439f8e7e948bae2ae5e9;m=2fef8cc5;t=58ddb4a186735;x=73cf19493edb5087
kernel:         5.1.17-300.fc30.x86_64
package:        gnome-calendar-3.32.2-1.fc30
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 77 Fedora Update System 2019-07-19 14:57:38 UTC 
FEDORA-2019-ff0223e2ca has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ff0223e2ca
Comment 78 Fedora Update System 2019-07-21 19:13:08 UTC 
FEDORA-2019-ff0223e2ca has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-ff0223e2ca
Comment 79 Fedora Update System 2019-07-22 01:10:06 UTC 
gnome-calendar-3.32.2-5.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-ff0223e2ca
Comment 80 Fedora Update System 2019-07-26 00:59:36 UTC 
gnome-calendar-3.32.2-5.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Comment 81 Michael Catanzaro 2019-09-03 12:02:07 UTC 
*** Bug 1727978 has been marked as a duplicate of this bug. ***
Comment 82 Michael Catanzaro 2019-09-03 12:02:12 UTC 
*** Bug 1729624 has been marked as a duplicate of this bug. ***
Comment 83 Michael Catanzaro 2019-09-03 12:02:17 UTC 
*** Bug 1729050 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.