Bug 2173204 - [abrt] gnome-calendar: g_type_check_instance_cast(): gnome-calendar killed by SIGSEGV
Summary: [abrt] gnome-calendar: g_type_check_instance_cast(): gnome-calendar killed by...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-calendar
Version: 37
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:097a7df52881ab113babff5506f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-24 18:14 UTC by Mohamed Baig
Modified: 2024-01-12 22:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-01-12 22:51:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (127.44 KB, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: core_backtrace (72.24 KB, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: cpuinfo (2.96 KB, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: dso_list (170 bytes, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: environ (1.38 KB, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: exploitable (82 bytes, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: limits (1.29 KB, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: maps (4.00 KB, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: mountinfo (3.02 KB, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: open_fds (8.09 KB, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: proc_pid_status (1.40 KB, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details
File: var_log_messages (1.58 KB, text/plain)
2023-02-24 18:14 UTC, Mohamed Baig
no flags Details

Description Mohamed Baig 2023-02-24 18:14:28 UTC
Description of problem:
Clicked to future day from the left nav then clicked back on today's date

Version-Release number of selected component:
gnome-calendar-43.1-3.fc37

Additional info:
reporter:       libreport-2.17.4
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.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=829bd94ca3fa4b64af263b98ea52b01f;i=da28c;b=5b2b156c38514bbe8228dc075ef7c8fa;m=2747c93f6;t=5f575d1e7b057;x=8f8db0b61ac96f1c
kernel:         6.1.13-200.fc37.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 g_type_check_instance_cast at ../gobject/gtype.c:4122
 #1 gcal_agenda_view_remove_event at ../src/gui/views/gcal-agenda-view.c:586
 #2 remove_event_from_subscriber at ../src/core/gcal-timeline.c:228
 #3 timeline_source_dispatch at ../src/core/gcal-timeline.c:717
 #6 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238
 #7 g_main_context_iteration at ../glib/gmain.c:4303
 #8 g_application_run at ../gio/gapplication.c:2571

Comment 1 Mohamed Baig 2023-02-24 18:14:32 UTC
Created attachment 1946213 [details]
File: backtrace

Comment 2 Mohamed Baig 2023-02-24 18:14:34 UTC
Created attachment 1946214 [details]
File: core_backtrace

Comment 3 Mohamed Baig 2023-02-24 18:14:35 UTC
Created attachment 1946215 [details]
File: cpuinfo

Comment 4 Mohamed Baig 2023-02-24 18:14:36 UTC
Created attachment 1946216 [details]
File: dso_list

Comment 5 Mohamed Baig 2023-02-24 18:14:37 UTC
Created attachment 1946217 [details]
File: environ

Comment 6 Mohamed Baig 2023-02-24 18:14:39 UTC
Created attachment 1946218 [details]
File: exploitable

Comment 7 Mohamed Baig 2023-02-24 18:14:40 UTC
Created attachment 1946219 [details]
File: limits

Comment 8 Mohamed Baig 2023-02-24 18:14:41 UTC
Created attachment 1946220 [details]
File: maps

Comment 9 Mohamed Baig 2023-02-24 18:14:42 UTC
Created attachment 1946221 [details]
File: mountinfo

Comment 10 Mohamed Baig 2023-02-24 18:14:44 UTC
Created attachment 1946222 [details]
File: open_fds

Comment 11 Mohamed Baig 2023-02-24 18:14:45 UTC
Created attachment 1946223 [details]
File: proc_pid_status

Comment 12 Mohamed Baig 2023-02-24 18:14:46 UTC
Created attachment 1946224 [details]
File: var_log_messages

Comment 13 Aoife Moloney 2023-11-23 01:19:39 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
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
'version' of '37'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 37 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 14 Aoife Moloney 2024-01-12 22:51:25 UTC
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05.

Fedora Linux 37 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.