Bug 1758200

Summary: [abrt] gnome-calendar: g_type_check_instance_cast(): gnome-calendar killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Ankur Sinha (FranciscoD) <sanjay.ankur>
Component: gnome-calendarAssignee: Igor Raits <igor.raits>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: gnome-sig, igor.raits
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2d95a5a2d2400ef2b059a9514c3a5695696cfbec
Whiteboard: abrt_hash:40b39a7047d4784f32b0da03439fb8e24ef6a609;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 16:39:06 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: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Ankur Sinha (FranciscoD) 2019-10-03 14:07:28 UTC
Description of problem:
Clicked on a checkbox to stop seeing a calendar, and it crashed.

Version-Release number of selected component:
gnome-calendar-3.34.0-2.fc31

Additional info:
reporter:       libreport-2.10.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dorg.gnome.Calendar.slice/dbus-:1.2-org.gnome.Calendar
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: g_type_check_instance_cast
executable:     /usr/bin/gnome-calendar
journald_cursor: s=f9783ab29e814b19a1ad32e9b6f8b268;i=336881;b=9b612b8de13b4547b7327d147e8abfa7;m=1ee4901ac;t=59401f8161d96;x=eef3a446680f44d9
kernel:         5.3.2-300.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 g_type_check_instance_cast at ../gobject/gtype.c:4060
 #1 remove_calendar at ../src/gui/gcal-calendar-popover.c:131
 #2 on_manager_calendar_changed_cb at ../src/gui/gcal-calendar-popover.c:219

Comment 1 Ankur Sinha (FranciscoD) 2019-10-03 14:07:31 UTC
Created attachment 1622318 [details]
File: backtrace

Comment 2 Ankur Sinha (FranciscoD) 2019-10-03 14:07:32 UTC
Created attachment 1622319 [details]
File: core_backtrace

Comment 3 Ankur Sinha (FranciscoD) 2019-10-03 14:07:33 UTC
Created attachment 1622320 [details]
File: cpuinfo

Comment 4 Ankur Sinha (FranciscoD) 2019-10-03 14:07:34 UTC
Created attachment 1622321 [details]
File: dso_list

Comment 5 Ankur Sinha (FranciscoD) 2019-10-03 14:07:35 UTC
Created attachment 1622322 [details]
File: environ

Comment 6 Ankur Sinha (FranciscoD) 2019-10-03 14:07:36 UTC
Created attachment 1622323 [details]
File: exploitable

Comment 7 Ankur Sinha (FranciscoD) 2019-10-03 14:07:37 UTC
Created attachment 1622324 [details]
File: limits

Comment 8 Ankur Sinha (FranciscoD) 2019-10-03 14:07:39 UTC
Created attachment 1622325 [details]
File: maps

Comment 9 Ankur Sinha (FranciscoD) 2019-10-03 14:07:40 UTC
Created attachment 1622326 [details]
File: mountinfo

Comment 10 Ankur Sinha (FranciscoD) 2019-10-03 14:07:41 UTC
Created attachment 1622327 [details]
File: open_fds

Comment 11 Ankur Sinha (FranciscoD) 2019-10-03 14:07:42 UTC
Created attachment 1622328 [details]
File: proc_pid_status

Comment 12 Ankur Sinha (FranciscoD) 2019-10-03 14:07:43 UTC
Created attachment 1622329 [details]
File: var_log_messages

Comment 13 Ankur Sinha (FranciscoD) 2019-10-08 14:39:41 UTC
Similar problem has been detected:

Another random crash.

reporter:       libreport-2.10.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-calendar --gapplication-service
crash_function: g_type_check_instance_cast
executable:     /usr/bin/gnome-calendar
journald_cursor: s=f9783ab29e814b19a1ad32e9b6f8b268;i=348dd2;b=9b612b8de13b4547b7327d147e8abfa7;m=24b64474ff;t=59466fb6710a0;x=11b3cc98f816ca2e
kernel:         5.3.2-300.fc31.x86_64
package:        gnome-calendar-3.34.0-2.fc31
reason:         gnome-calendar killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Ben Cotton 2020-11-03 15:37:36 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 Ben Cotton 2020-11-24 16:39:06 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.