Description of problem: In the month-view, clicking quickly into the past month by month. I use calendars being local, on google, on nexcloud and via an exchange connection. Language used in German. Version-Release number of selected component: gnome-calendar-3.32.0-1.fc30 Additional info: 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=7e90057a777b4e8cbaa5994c0e4eb675;i=1863e;b=576b295544574575b2e7fe048bdd2d2f;m=c6425d7d2;t=58838aad6f6e5;x=7459381d4d20aed6 kernel: 5.0.11-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_image_reset at gtkimage.c:1910 #1 gtk_image_clear at gtkimage.c:1910 #2 update_weather at ../src/views/gcal-year-view.c:2121 #3 update_no_events_page at ../src/views/gcal-year-view.c:301 #4 gcal_year_view_component_removed at ../src/views/gcal-year-view.h:32 #5 gcal_year_view_component_changed at ../src/views/gcal-year-view.c:1934 #6 cal_data_model_foreach_subscriber_in_range at ../contrib/evolution/e-cal-data-model.c:619 #7 cal_data_model_process_added_component at ../contrib/evolution/e-cal-data-model.c:962 #8 cal_data_model_process_modified_or_added_objects at ../contrib/evolution/e-cal-data-model.c:1307 #9 g_cclosure_marshal_VOID__POINTERv at ../gobject/gmarshal.c:1800 Potential duplicate: bug 1561868
Created attachment 1564500 [details] File: backtrace
Created attachment 1564501 [details] File: cgroup
Created attachment 1564502 [details] File: core_backtrace
Created attachment 1564503 [details] File: cpuinfo
Created attachment 1564504 [details] File: dso_list
Created attachment 1564505 [details] File: environ
Created attachment 1564506 [details] File: exploitable
Created attachment 1564507 [details] File: limits
Created attachment 1564508 [details] File: maps
Created attachment 1564509 [details] File: mountinfo
Created attachment 1564510 [details] File: open_fds
Created attachment 1564511 [details] File: proc_pid_status
Created attachment 1564512 [details] File: var_log_messages
Similar problem has been detected: I changed one instance of a repeated event that is synced with a google account. Then I closed the app. 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=41a16d2e06f34d3c829103581234d198;i=c611;b=bfe804c8fe1f4e069ab8442d7fe2ba33;m=3d7fb327f;t=588eb79f44503;x=e1cb7889226432e4 kernel: 5.0.14-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
*** Bug 1710651 has been marked as a duplicate of this bug. ***
*** Bug 1710705 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Don't know how it happen, except that I was alerted after bringing the workstation back from hibernation. 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=c0192dfc531742b1831933d40d554bd8;i=223fe;b=75cbe7c44b3a4682b3c6140d31cff7cb;m=942c37f;t=5893c87827780;x=3e3d0b13bcf95dad kernel: 5.0.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
*** Bug 1714097 has been marked as a duplicate of this bug. ***
*** Bug 1716121 has been marked as a duplicate of this bug. ***
*** Bug 1716435 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Potential reason might be, that I added a new remote calendar to a google account and this calendar might unexpectedly have shown up on a communication between the application and the google account? 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=282a1c7f898148558cb502d27014b491;i=b742;b=4566e334447644eaaac6abeda920ef1c;m=140226bf19;t=58aa4adef3fa1;x=143a9ec62cb15eb4 kernel: 5.1.5-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
*** Bug 1718550 has been marked as a duplicate of this bug. ***
*** Bug 1723913 has been marked as a duplicate of this bug. ***
*** Bug 1724070 has been marked as a duplicate of this bug. ***
*** Bug 1724172 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Changing an all day - three week event, to another roughy three week event with start and end times. First I changed the end date and time, the the begin date and time. Then this crash occurred. The calendar is hosted on Nextcloud (remote). 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=d8763f452d994763ba2a13536bd915d4;i=2e14ce;b=3c5194566ffc4488b61197b002c0550b;m=14c27eb9f0;t=58c3a9bfdf5ba;x=94d0def367977b7d kernel: 5.1.12-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
*** Bug 1726647 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 1561868 ***
*** Bug 1727978 has been marked as a duplicate of this bug. ***
*** Bug 1729050 has been marked as a duplicate of this bug. ***
*** Bug 1729624 has been marked as a duplicate of this bug. ***
*** Bug 1740448 has been marked as a duplicate of this bug. ***