Description of problem: Calendar crashed while I was searching for events. Version-Release number of selected component: gnome-calendar-44~rc-1.fc38 Additional info: reporter: libreport-2.17.8 type: CCpp reason: gnome-calendar killed by SIGSEGV journald_cursor: s=f14ac85b1ea64de087f79c5fe57e0ea5;i=182ace;b=dea6d4e9b8bd44e39c68387c509e0aff;m=49d32752a;t=5f68ce6f8c258;x=36bd6671bd7dd702 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.2.2-301.fc38.x86_64 package: gnome-calendar-44~rc-1.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: _g_list_remove_link comment: Calendar crashed while I was searching for events. Truncated backtrace: Thread no. 1 (16 frames) #0 _g_list_remove_link at ../glib/glist.c:563 #1 g_list_remove_link at ../glib/glist.c:675 #2 g_queue_unlink at ../glib/gqueue.c:847 #3 g_queue_delete_link at ../glib/gqueue.c:869 #4 queue_event_data at ../src/core/gcal-timeline.c:163 #5 on_calendar_monitor_event_removed_cb at ../src/core/gcal-timeline.c:559 #6 g_cclosure_marshal_VOID__OBJECTv at ../gobject/gmarshal.c:1910 #7 _g_closure_invoke_va at ../gobject/gclosure.c:895 #10 remove_events_outside_range at ../src/core/gcal-calendar-monitor.c:1005 #11 gcal_calendar_monitor_set_range at ../src/core/gcal-calendar-monitor.c:1349 #12 update_range at ../src/core/gcal-timeline.c:289 #13 gcal_timeline_add_subscriber at ../src/core/gcal-timeline.c:995 #14 search_func at ../src/search/gcal-search-engine.c:103 #15 g_task_thread_pool_thread at ../gio/gtask.c:1531 #17 g_thread_proxy at ../glib/gthread.c:831 #19 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Potential duplicate: bug {crossver_id}
Created attachment 1949588 [details] File: proc_pid_status
Created attachment 1949589 [details] File: maps
Created attachment 1949590 [details] File: limits
Created attachment 1949591 [details] File: environ
Created attachment 1949592 [details] File: open_fds
Created attachment 1949593 [details] File: mountinfo
Created attachment 1949594 [details] File: os_info
Created attachment 1949595 [details] File: cpuinfo
Created attachment 1949596 [details] File: core_backtrace
Created attachment 1949597 [details] File: exploitable
Created attachment 1949598 [details] File: dso_list
Created attachment 1949599 [details] File: var_log_messages
Created attachment 1949600 [details] File: backtrace
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/988
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-21. 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 '38'. 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 38 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.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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.