Description of problem: adding a location to a calendar entry Version-Release number of selected component: gnome-calendar-43.1-3.fc37 Additional info: reporter: libreport-2.17.4 backtrace_rating: 3 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: _gtk_widget_is_sensitive executable: /usr/bin/gnome-calendar journald_cursor: s=8b593f4d013b441aa2224344ad125a83;i=1d7186;b=9ef4199959dd46e394d85341b0cbff5f;m=1e833045d;t=5f650ba8ba4bf;x=7948b4ef321892b2 kernel: 6.1.14-200.fc37.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _gtk_widget_is_sensitive at ../gtk/gtkwidgetprivate.h:491 #1 gtk_propagate_event_internal.isra.0 at ../gtk/gtkmain.c:1895 #2 gtk_main_do_event at ../gtk/gtkmain.c:1680 #3 surface_event at ../gtk/gtkwindow.c:4735 #4 _gdk_marshal_BOOLEAN__POINTERv at gdk/gdkmarshalers.c:302 #5 gdk_surface_event_marshallerv at ../gdk/gdksurface.c:463 #6 g_signal_group__target_weak_notify at ../gobject/gsignalgroup.c:163 #7 g_list_insert_before at ../glib/glist.c:478 #8 ?? #9 ??
Created attachment 1948691 [details] File: backtrace
Created attachment 1948692 [details] File: core_backtrace
Created attachment 1948693 [details] File: cpuinfo
Created attachment 1948694 [details] File: dso_list
Created attachment 1948695 [details] File: environ
Created attachment 1948696 [details] File: exploitable
Created attachment 1948697 [details] File: limits
Created attachment 1948698 [details] File: maps
Created attachment 1948699 [details] File: mountinfo
Created attachment 1948700 [details] File: open_fds
Created attachment 1948701 [details] File: proc_pid_status
Created attachment 1948702 [details] File: var_log_messages
Similar problem has been detected: Just opened my calendar and clicked on an event. The event info popped up, and then the calendar crashed. I have the calendar linked to a Google account, and the event was an event from that calendar. reporter: libreport-2.17.4 backtrace_rating: 4 cgroup: 0::/user.slice/user-1005.slice/user/app.slice/dbus-:1.2-org.gnome.Calendar cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: _gtk_widget_is_sensitive dso_list: /usr/bin/gnome-calendar gnome-calendar-43.1-3.fc37.x86_64 (Fedora Project) 1667638821 executable: /usr/bin/gnome-calendar journald_cursor: s=010069dca3394e9c808b3a723cf620ea;i=1e6a6;b=e6fad728f8394b2080824a9cdf232d75;m=12659ff38;t=5f833ec3305ad;x=c7948bde97c21998 kernel: 6.2.8-200.fc37.x86_64 package: gnome-calendar-43.1-3.fc37 reason: gnome-calendar killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1005
Created attachment 1954919 [details] File: backtrace
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.
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.