Bug 1630767 - [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 DUPLICATE of bug 1561868
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-calendar
Version: 29
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...
: 1644891 1645868 1666898 1671066 1671596 1671896 1671969 1677084 1677865 1683327 1690438 1693666 1694775 1695857 1696236 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-19 08:46 UTC by Lukas Ruzicka
Modified: 2019-07-03 15:15 UTC (History)
33 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-07-03 15:15:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (67.56 KB, text/plain)
2018-09-19 08:46 UTC, Lukas Ruzicka 		no flags Details
File: cgroup (355 bytes, text/plain)
2018-09-19 08:46 UTC, Lukas Ruzicka 		no flags Details
File: core_backtrace (16.05 KB, text/plain)
2018-09-19 08:46 UTC, Lukas Ruzicka 		no flags Details
File: cpuinfo (1.30 KB, text/plain)
2018-09-19 08:46 UTC, Lukas Ruzicka 		no flags Details
File: dso_list (21.53 KB, text/plain)
2018-09-19 08:46 UTC, Lukas Ruzicka 		no flags Details
File: environ (1.59 KB, text/plain)
2018-09-19 08:46 UTC, Lukas Ruzicka 		no flags Details
File: exploitable (82 bytes, text/plain)
2018-09-19 08:46 UTC, Lukas Ruzicka 		no flags Details
File: limits (1.29 KB, text/plain)
2018-09-19 08:47 UTC, Lukas Ruzicka 		no flags Details
File: maps (135.52 KB, text/plain)
2018-09-19 08:47 UTC, Lukas Ruzicka 		no flags Details
File: mountinfo (3.70 KB, text/plain)
2018-09-19 08:47 UTC, Lukas Ruzicka 		no flags Details
File: open_fds (1.21 KB, text/plain)
2018-09-19 08:47 UTC, Lukas Ruzicka 		no flags Details
File: proc_pid_status (1.31 KB, text/plain)
2018-09-19 08:47 UTC, Lukas Ruzicka 		no flags Details
File: var_log_messages (1.29 KB, text/plain)
2018-09-19 08:47 UTC, Lukas Ruzicka 		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-02-26 22:25:58 UTC
GNOME Gitlab GNOME/gnome-calendar/issues/338 0 None None None 2019-02-26 22:27:18 UTC

Description Lukas Ruzicka 2018-09-19 08:46:45 UTC 
Description of problem:
I wanted to run an application, started to write in the search field, when it crashed.

Version-Release number of selected component:
gnome-calendar-3.30.0-1.fc29

Additional info:
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=fb387e8b01d14d5abef03bf0faa05845;i=2f5c;b=6b4cb2e5ea5f40e4a5c9774052ea897d;m=5114b11a;t=576354619c78f;x=506106c1699116ed
kernel:         4.18.7-300.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1342

Truncated backtrace:
Thread no. 1 (10 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: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 cal_data_model_foreach_subscriber_in_range at ../contrib/evolution/e-cal-data-model.c:619
 #6 cal_data_model_view_objects_removed at ../contrib/evolution/e-cal-data-model.c:1438
 #7 g_cclosure_marshal_VOID__POINTERv at gmarshal.c:2026
 #8 _g_closure_invoke_va at gclosure.c:873
 #11 cal_client_view_emit_objects_removed_idle_cb at /usr/src/debug/evolution-data-server-3.30.0-1.fc29.x86_64/src/calendar/libecal/e-cal-client-view.c:253

Potential duplicate: bug 1609498
Comment 1 Lukas Ruzicka 2018-09-19 08:46:51 UTC 
Created attachment 1484592 [details]
File: backtrace
Comment 2 Lukas Ruzicka 2018-09-19 08:46:52 UTC 
Created attachment 1484593 [details]
File: cgroup
Comment 3 Lukas Ruzicka 2018-09-19 08:46:53 UTC 
Created attachment 1484594 [details]
File: core_backtrace
Comment 4 Lukas Ruzicka 2018-09-19 08:46:54 UTC 
Created attachment 1484595 [details]
File: cpuinfo
Comment 5 Lukas Ruzicka 2018-09-19 08:46:56 UTC 
Created attachment 1484596 [details]
File: dso_list
Comment 6 Lukas Ruzicka 2018-09-19 08:46:57 UTC 
Created attachment 1484597 [details]
File: environ
Comment 7 Lukas Ruzicka 2018-09-19 08:46:59 UTC 
Created attachment 1484598 [details]
File: exploitable
Comment 8 Lukas Ruzicka 2018-09-19 08:47:00 UTC 
Created attachment 1484599 [details]
File: limits
Comment 9 Lukas Ruzicka 2018-09-19 08:47:02 UTC 
Created attachment 1484600 [details]
File: maps
Comment 10 Lukas Ruzicka 2018-09-19 08:47:03 UTC 
Created attachment 1484601 [details]
File: mountinfo
Comment 11 Lukas Ruzicka 2018-09-19 08:47:04 UTC 
Created attachment 1484602 [details]
File: open_fds
Comment 12 Lukas Ruzicka 2018-09-19 08:47:05 UTC 
Created attachment 1484603 [details]
File: proc_pid_status
Comment 13 Lukas Ruzicka 2018-09-19 08:47:06 UTC 
Created attachment 1484604 [details]
File: var_log_messages
Comment 14 Christian Stadelmann 2018-10-08 08:02:49 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=4f00aa;b=35f0936881ee437e9d8987f4fef05fd7;m=906deb8eb;t=577a9e52ddfbe;x=d17026fae60b8979
kernel:         4.18.11-301.fc29.x86_64
package:        gnome-calendar-3.30.0-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
Comment 15 Christian Stadelmann 2018-10-09 13:47:08 UTC 
Similar problem has been detected:

GNOME calendar crashes every time I close it.

reporter:       libreport-2.9.6
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=50250b;b=30bcd6b182ea48219b7590a532564a62;m=c419adcd5;t=577cbec041372;x=182fa3064e5ef802
kernel:         4.18.12-300.fc29.x86_64
package:        gnome-calendar-3.30.0-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
Comment 16 Christian Stadelmann 2018-10-09 19:32:47 UTC 
Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/299

Workaround: Disable weather integration from main menu.
Comment 17 Christian Stadelmann 2018-10-10 13:06:43 UTC 
Similar problem has been detected:

Every time I close gnome-calendar, it crashes.

reporter:       libreport-2.9.6
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=508577;b=42edbb91d9814331aaea73d8fa07967f;m=4ab0cef08;t=577df3670aadb;x=3e652a498d68f8b1
kernel:         4.18.12-300.fc29.x86_64
package:        gnome-calendar-3.30.0-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
Comment 18 Christian Stadelmann 2018-10-10 13:26:26 UTC 
(In reply to Christian Stadelmann from comment #16)
> Upstream bug report: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/299
> 
> Workaround: Disable weather integration from main menu.

That workaround does not seem to work… :(
Comment 19 ricky.tigg 2018-10-18 09:22:06 UTC 
Similar problem has been detected:

II clicked  a notification.

reporter:       libreport-2.9.6
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=0b5b00661aac41b0934eeae5680a5bda;i=134ab4;b=15418e65871b46f0afbd85824ddf7624;m=6d6b3d61;t=5787d2cc82eb9;x=c314848d6f4069d2
kernel:         4.18.12-300.fc29.x86_64
package:        gnome-calendar-3.30.0-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 20 Sebastian Birk 2018-10-31 20:05:23 UTC 
*** Bug 1644891 has been marked as a duplicate of this bug. ***
Comment 21 Ashesh Singh 2018-11-04 14:48:01 UTC 
*** Bug 1645868 has been marked as a duplicate of this bug. ***
Comment 22 Yajo 2018-11-08 13:47:21 UTC 
Similar problem has been detected:

I updated an event title.
The event had repetition, so when editing, I chose to edit only that instance.
The event came from a Google Calendar.
I closed the app after that.

reporter:       libreport-2.9.6
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=d980a01b16544c1eb77ce181038a0903;i=38a64d;b=d27cd7752818451795d8a48f394be69c;m=88409b5b4;t=57a260b701e6e;x=78bc15f252496330
kernel:         4.18.16-300.fc29.x86_64
package:        gnome-calendar-3.30.0-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 23 Ivan 2018-11-13 15:59:31 UTC 
Similar problem has been detected:

I add a new event for today, then edit event details to add note for that event, the event gets moved to yesterday. I drag the event manually back to today's box, and open event details to see if they are correct. They are, and I click 'done' to close event details window after which gnome calendar crashes and event gets moved back to yesterday.

reporter:       libreport-2.9.6
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=35add27b4ba94c13a7a028e42243b69e;i=3ac1;b=e970d781d641410188f9fce705fecc72;m=1191b160b;t=57a8dc97f07a5;x=84cc374b036fc7ca
kernel:         4.18.17-300.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 24 rugk 2018-12-19 23:21:06 UTC 
Similar problem has been detected:

switched to Jan 2019

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=1b1e899daa404e5fb64d5fbb2fadc896;i=32da78;b=ba38b5a0aff740b39d0009c24a7e8bbe;m=9cda41854;t=57d682846c2db;x=2081f9e0781b9b32
kernel:         4.19.9-300.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 25 Dan 2019-01-16 21:30:44 UTC 
*** Bug 1666898 has been marked as a duplicate of this bug. ***
Comment 26 msandova 2019-01-19 15:01:29 UTC 
Similar problem has been detected:

I am using gnome-calendar together with a caldav (radicale) host. After creating entries the calendar sometimes just crashes. The entry gets succefully created just before the crash. 

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
environ:        "Personally identifiable information"
executable:     /usr/bin/gnome-calendar
journald_cursor: s=5086ac8d83164cca8a3871e0d448d637;i=5ecb3;b=8c45478bf9c54684ae72e65f4605534a;m=1b63a4667;t=57fbc46921f33;x=a0111877ede5126f
kernel:         4.19.14-300.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 27 Kevin McCormack 2019-01-30 16:46:16 UTC 
*** Bug 1671066 has been marked as a duplicate of this bug. ***
Comment 28 Joe Walker 2019-02-01 00:59:10 UTC 
Similar problem has been detected:

Restarted computer with no network connection. 

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=745a5cd9436149f68438827863c772eb;i=88ce;b=3abed53543cf41e6b101cd62b9c626d3;m=5a0c191b;t=580607eb15dc4;x=5e53758cd10db4fb
kernel:         4.20.3-200.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 29 Joe Walker 2019-02-01 01:25:59 UTC 
Similar problem has been detected:

Restart Computer without network collection, select clock to display calendar. 

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: gtk_image_reset
executable:     /usr/bin/gnome-calendar
journald_cursor: s=745a5cd9436149f68438827863c772eb;i=1fb11;b=b6e5c5c6f7ff41e7a74bd74bfb103316;m=228f0e6e3;t=580cabb159645;x=c09bc39ed1c89a58
kernel:         4.20.4-200.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 30 Jim Nelson 2019-02-01 01:34:59 UTC 
*** Bug 1671596 has been marked as a duplicate of this bug. ***
Comment 31 Jim Nelson 2019-02-02 03:23:56 UTC 
*** Bug 1671896 has been marked as a duplicate of this bug. ***
Comment 32 Ben Spera 2019-02-02 22:07:33 UTC 
*** Bug 1671969 has been marked as a duplicate of this bug. ***
Comment 33 Jim Nelson 2019-02-14 00:58:08 UTC 
*** Bug 1677084 has been marked as a duplicate of this bug. ***
Comment 34 Jean-Loup Tastet 2019-02-15 13:59:28 UTC 
Similar problem has been detected:

Here are the steps which lead to the crash:
- Open Calendar
- Delete one instance of a recurrent event
- Close Calendar
The ABRT notification showed up a few seconds after closing Calendar.

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=a1eb554087f6453b8b4b2de8a4975da3;i=7c6f9;b=59f525bbca6645e2af492c9aa1d8ffc8;m=39a591232;t=581eefa6d8fda;x=cf08d49f75a6999
kernel:         4.18.16-300.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 35 Subhadeep Dey 2019-02-16 13:55:32 UTC 
*** Bug 1677865 has been marked as a duplicate of this bug. ***
Comment 36 Jean-Loup Tastet 2019-02-26 09:36:46 UTC 
Similar problem has been detected:

The crash happened after trying to reproduce https://gitlab.gnome.org/GNOME/gnome-calendar/issues/338.

See this screencast: https://gitlab.gnome.org/GNOME/gnome-calendar/issues/338#note_446254
The crash happened a few seconds after the end of the screencast.

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=e0727d9a8a414c4f8f45be933af8b75a;i=d70;b=f6ad5644f8b04cdfaf7cadf514679930;m=81a2b31b;t=582c856b721f6;x=c9c0354b9c9afdb5
kernel:         4.20.10-200.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 37 Jim Nelson 2019-02-26 15:45:36 UTC 
*** Bug 1683327 has been marked as a duplicate of this bug. ***
Comment 38 Ankur Sinha (FranciscoD) 2019-02-26 22:24:44 UTC 
Similar problem has been detected:

Modifed an event, but it didn't update in the app. Modified it on Google, closed and re-opened the app but the event hadnt been updated. Clicked "synchronise", app crashed.

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=3e04612fecab4abe94134e84667ede4f;i=5089f1;b=e753ba84c6334d19a5244808109a9058;m=54024e397b;t=582d3624b391e;x=ebad85db5251f377
kernel:         4.20.7-200.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 39 Ryan Quinn 2019-03-06 16:38:49 UTC 
Similar problem has been detected:

Closed Calender.

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=1bfa2c2d2d1d448eab15b8385c2ad72c;i=200a9;b=99c8ef8bafbc4eae950edd9048061941;m=2166adeb17;t=5836f81749fb1;x=43e0c9c754e2d44e
kernel:         4.20.13-200.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 40 Jean-Loup Tastet 2019-03-07 21:28:59 UTC 
Similar problem has been detected:

The crash occured after deleting one instance of a recurring event, and then closing gnome-calendar.

Steps to reproduce:
1. Create a recurring event, repeating weekly, forever
2. Delete one instance of this recurring event
3. Close gnome-calendar

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=e0727d9a8a414c4f8f45be933af8b75a;i=2b086;b=2f2b930683f74410b7b53c10e5dfb08d;m=7b275d80;t=58387b74ca243;x=f0016677303c80e3
kernel:         4.16.0-2.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 41 aoellerer 2019-03-19 13:36:44 UTC 
*** Bug 1690438 has been marked as a duplicate of this bug. ***
Comment 42 Paulo Falcao 2019-03-28 12:44:17 UTC 
*** Bug 1693666 has been marked as a duplicate of this bug. ***
Comment 43 Alex Bradatan 2019-03-31 11:22:11 UTC 
Similar problem has been detected:

I added a new account in the settings and then came back to the Calendar app and it crashed.
The new account was a Microsoft account without support for calendar syncing.

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=72022188bcf8429b9e66ece274616b5a;i=244e3;b=54bb0cc41a504381a7f38fa0729d919b;m=8da76c05;t=58561e990266a;x=5bb77ab005e1bf3
kernel:         5.0.4-200.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 44 marcus.wi 2019-04-01 15:50:17 UTC 
*** Bug 1694775 has been marked as a duplicate of this bug. ***
Comment 45 0x.casey 2019-04-02 18:34:55 UTC 
*** Bug 1695277 has been marked as a duplicate of this bug. ***
Comment 46 cecco.se.it 2019-04-03 19:50:23 UTC 
*** Bug 1695857 has been marked as a duplicate of this bug. ***
Comment 47 Jonathas Botelho 2019-04-04 11:51:59 UTC 
*** Bug 1696236 has been marked as a duplicate of this bug. ***
Comment 48 krinkodot22 2019-04-07 20:21:52 UTC 
Similar problem has been detected:

First, I tried opening a *.ics file by double-clicking on one attached to an email in Evolution (with Calendar set as my default program to open events). When nothing happened, I tried opening a Calendar window by opening Gnome Shell's notification area, clicking on a date in the calendar on the right, and then clicking on the name of that date in the top-left corner of the area. Doing that did not open a Calendar window either, and shortly afterwards, this crash occurred.

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=bec4244868c146e9a10f46825fb1cabc;i=148f65;b=f1dcc3f6f11f4f2cb3fd9528cfcf8459;m=3d82c804e;t=585f6494b6c69;x=1f300d6e7e068d9b
kernel:         5.0.5-200.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 49 krinkodot22 2019-04-29 05:15:12 UTC 
Similar problem has been detected:

Deleted an event from the calendar, then closed the window. A few moments later, this crash happened.

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=c228e1adbf734ffb85d748f6f7e66196;i=110931;b=197ee184ac0f488f9d3bc43ad96f4fa5;m=aafb7ea69;t=587a4477c2b33;x=3f342e36525e68aa
kernel:         5.0.9-200.fc29.x86_64
package:        gnome-calendar-3.30.1-1.fc29
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 50 Michael Catanzaro 2019-07-03 15:15:22 UTC 

*** This bug has been marked as a duplicate of bug 1561868 ***
Note You need to log in before you can comment on or make changes to this bug.