Description of problem: I exit the application like I normally would using the X in the top right Version-Release number of selected component: gnome-calendar-46.0-1.fc40 Additional info: reporter: libreport-2.17.15 type: CCpp reason: gnome-calendar killed by SIGSEGV journald_cursor: s=907e1d0e7af84b4996007471e0e52560;i=e85e;b=c07dbd45ceb0489bb28fd7eed8474486;m=5e8237bb;t=6151e421587b6;x=ad10ac7c5eda6653 executable: /usr/bin/gnome-calendar cmdline: /usr/bin/gnome-calendar --gapplication-service cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Calendar rootdir: / uid: 1000 kernel: 6.8.2-300.fc40.x86_64 package: gnome-calendar-46.0-1.fc40 runlevel: N 5 backtrace_rating: 4 crash_function: g_type_check_instance_is_fundamentally_a comment: I exit the application like I normally would using the X in the top right Truncated backtrace: Thread no. 1 (14 frames) #0 g_type_check_instance_is_fundamentally_a at ../gobject/gtype.c:4154 #2 on_gclue_client_stopped_cb at ../src/weather/gcal-weather-service.c:810 #3 g_task_return_now at ../gio/gtask.c:1361 #4 g_task_return at ../gio/gtask.c:1430 #6 reply_cb at ../gio/gdbusproxy.c:2555 #7 g_task_return_now at ../gio/gtask.c:1361 #8 g_task_return at ../gio/gtask.c:1430 #10 g_dbus_connection_call_done at ../gio/gdbusconnection.c:5897 #11 g_task_return_now at ../gio/gtask.c:1361 #12 complete_in_idle_cb at ../gio/gtask.c:1375 #15 g_main_context_dispatch_unlocked at ../glib/gmain.c:4152 #16 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4217 #17 g_main_context_iteration at ../glib/gmain.c:4282 #18 g_application_run at ../gio/gapplication.c:2712
Created attachment 2024788 [details] File: proc_pid_status
Created attachment 2024789 [details] File: maps
Created attachment 2024790 [details] File: limits
Created attachment 2024791 [details] File: environ
Created attachment 2024792 [details] File: open_fds
Created attachment 2024793 [details] File: mountinfo
Created attachment 2024794 [details] File: os_info
Created attachment 2024795 [details] File: cpuinfo
Created attachment 2024796 [details] File: core_backtrace
Created attachment 2024797 [details] File: exploitable
Created attachment 2024798 [details] File: dso_list
Created attachment 2024799 [details] File: var_log_messages
Created attachment 2024800 [details] File: backtrace
Launched the Calendar app from the dock. Left the Calendar app open for a number of minutes. When I clicked to close the Calendar app the error came up saying gnome-calendar quit unexpectedly. reporter: libreport-2.17.15 type: CCpp reason: gnome-calendar killed by SIGSEGV journald_cursor: s=9e16964a36c147c4ab586a430c526cdc;i=477a;b=29831677b3e348ad850b1dd2f93254b5;m=6d7ae1db;t=616ccac5723ea;x=aac051db688643e5 executable: /usr/bin/gnome-calendar cmdline: /usr/bin/gnome-calendar --gapplication-service cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Calendar rootdir: / uid: 1000 kernel: 6.8.7-300.fc40.x86_64 package: gnome-calendar-46.0-1.fc40 runlevel: N 5 backtrace_rating: 4 crash_function: g_type_check_instance_is_fundamentally_a comment: Launched the Calendar app from the dock. Left the Calendar app open for a number of minutes. When I clicked to close the Calendar app the error came up saying gnome-calendar quit unexpectedly.
Opened the calendar app from notification. Looked at some events, closed calender, then error notification popped up reporter: libreport-2.17.15 type: CCpp reason: gnome-calendar killed by SIGSEGV journald_cursor: s=85a47127845043919b5cd3f2fe90cdb6;i=4864;b=86ce171e481e41689a4e3ff651a161e1;m=11f026523;t=619310769d590;x=df9b9a39bec0bd7f executable: /usr/bin/gnome-calendar cmdline: /usr/bin/gnome-calendar --gapplication-service cgroup: 0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.gnome.Calendar rootdir: / uid: 1000 kernel: 6.8.10-300.fc40.x86_64 package: gnome-calendar-46.1-1.fc40 runlevel: N 5 backtrace_rating: 4 crash_function: g_type_check_instance_is_fundamentally_a comment: Opened the calendar app from notification. Looked at some events, closed calender, then error notification popped up
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. 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 '40'. 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 40 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.
Bug reports for this component on Red Hat Bugzilla are not actively monitored. Please consider reporting your issue directly to GNOME at https://gitlab.gnome.org/GNOME/ to improve the chances that your issue will be resolved. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 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.