Description of problem: I edited an event and typed "Prague" into the Location field, then hit Save, and it crashed. 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=182149;b=dea6d4e9b8bd44e39c68387c509e0aff;m=415c9dd48;t=5f68c5f902a76;x=50a38c7ce484216f 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 dso_list: /usr/bin/gnome-calendar gnome-calendar-44~rc-1.fc38.x86_64 (Fedora Project) 1678436218 backtrace_rating: 4 crash_function: _gtk_widget_is_sensitive comment: I edited an event and typed "Prague" into the Location field, then hit Save, and it crashed. Truncated backtrace: Thread no. 1 (16 frames) #0 _gtk_widget_is_sensitive at ../gtk/gtkwidgetprivate.h:482 #1 gtk_propagate_event_internal.isra.0 at ../gtk/gtkmain.c:1918 #2 gtk_main_do_event at ../gtk/gtkmain.c:1703 #3 surface_event at ../gtk/gtkwindow.c:4747 #4 _gdk_marshal_BOOLEAN__POINTERv at gdk/gdkmarshalers.c:302 #5 gdk_surface_event_marshallerv at ../gdk/gdksurface.c:463 #6 _g_closure_invoke_va at ../gobject/gclosure.c:895 #9 gdk_surface_handle_event.isra.0 at ../gdk/gdksurface.c:2956 #10 gdk_surface_ensure_motion at ../gdk/gdksurface.c:2473 #11 gdk_surface_flush_events at ../gdk/gdksurface.c:2484 #13 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3802 #16 _gdk_frame_clock_emit_flush_events at ../gdk/gdkframeclock.c:668 #17 gdk_frame_clock_flush_idle at ../gdk/gdkframeclockidle.c:369 #21 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #22 g_main_context_iteration at ../glib/gmain.c:4343 #23 g_application_run at ../gio/gapplication.c:2573 Potential duplicate: bug {crossver_id}
Created attachment 1949576 [details] File: proc_pid_status
Created attachment 1949577 [details] File: maps
Created attachment 1949578 [details] File: limits
Created attachment 1949579 [details] File: environ
Created attachment 1949580 [details] File: open_fds
Created attachment 1949581 [details] File: mountinfo
Created attachment 1949582 [details] File: os_info
Created attachment 1949583 [details] File: cpuinfo
Created attachment 1949584 [details] File: core_backtrace
Created attachment 1949585 [details] File: exploitable
Created attachment 1949586 [details] File: var_log_messages
Created attachment 1949587 [details] File: backtrace
I found out more details: * The event needs to be from Google calendar (or possibly other remote source), it doesn't crash with a local calendar * This is not about location, it also happens when I edit e.g. the event name * To trigger this, I have to click on the event quite quickly after confirming the change. It seems that if I click on the event before the change is submitted to Google servers and then refreshed, it triggers this problem. If I wait for a few seconds and then click on the event, it's fine. * There are two options, either it crashes, or the window becomes unresponsive, nothing can be clicked on, and it can't be closed either (gnome-shell doesn't invoke the unresponsive window dialog, so the only option is to send sigterm to the process, to close the window).
Upstream bug: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/986
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.