Description of problem: Tried to synchronize an event on Google Calendar (which had been modified at the same time) and then I opened its window, and finally the application crashed (I guess because it was trying to update the event whose window were open). Version-Release number of selected component: gnome-calendar-3.18.1-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: icaltime_day_of_year executable: /usr/bin/gnome-calendar global_pid: 9448 kernel: 4.2.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 icaltime_day_of_year at /usr/src/debug/libical-1.0.1/src/libical/icaltime.c:604 #1 gcal_year_view_component_added at gcal-year-view.c:1145 #2 cal_data_model_foreach_subscriber_in_range at e-cal-data-model.c:623 #3 cal_data_model_process_added_component at e-cal-data-model.c:905 #4 cal_data_model_process_modified_or_added_objects at e-cal-data-model.c:1248 #5 g_cclosure_marshal_VOID__POINTERv at gmarshal.c:2026 #6 _g_closure_invoke_va at gclosure.c:864 #9 cal_client_view_emit_objects_modified_idle_cb at e-cal-client-view.c:236 #14 gtk_dialog_run at gtkdialog.c:1395 #15 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102 Potential duplicate: bug 1214596
Created attachment 1090961 [details] File: backtrace
Created attachment 1090962 [details] File: cgroup
Created attachment 1090963 [details] File: core_backtrace
Created attachment 1090964 [details] File: dso_list
Created attachment 1090965 [details] File: environ
Created attachment 1090966 [details] File: exploitable
Created attachment 1090967 [details] File: limits
Created attachment 1090968 [details] File: maps
Created attachment 1090969 [details] File: mountinfo
Created attachment 1090970 [details] File: open_fds
Created attachment 1090971 [details] File: proc_pid_status
Created attachment 1090972 [details] File: var_log_messages
Another user experienced a similar problem: guess it was after changing a calendar entry and sending the laptop intosleep mode afterwards... ? reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: icaltime_day_of_year executable: /usr/bin/gnome-calendar global_pid: 8744 kernel: 4.2.5-300.fc23.x86_64 package: gnome-calendar-3.18.1-1.fc23 reason: gnome-calendar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
*** Bug 1214596 has been marked as a duplicate of this bug. ***
*** Bug 1340186 has been marked as a duplicate of this bug. ***
*** Bug 1321411 has been marked as a duplicate of this bug. ***
Similar problem has been detected: I just opened and closed it. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: icaltime_day_of_year executable: /usr/bin/gnome-calendar global_pid: 3051 kernel: 4.6.3-300.fc24.x86_64 package: gnome-calendar-3.20.2-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-calendar killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1000
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
Similar problem has been detected: This is what happened: * There was a calendar in the list that had been created by another application. I think it was created by a Thunderbird extension (https://addons.mozilla.org/en-US/thunderbird/addon/eds-calendar-integration/). I had disabled that extension and rebooted the system since then. * I closed and opened GNOME Calendar. No events were shown on it, even for enabled calendars. The deleted calendar was on the list of calendars again. * I clicked on the deleted calendar to re-enable it and the application crashed. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: icaltime_day_of_year executable: /usr/bin/gnome-calendar global_pid: 4775 kernel: 4.6.4-301.fc24.x86_64 package: gnome-calendar-3.20.2-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-calendar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Forgot one step in the middle: (In reply to Jacobo Aragunde from comment #19) > * There was a calendar in the list that had been created by another > application. [...] > * Removed that calendar. > * I closed and opened GNOME Calendar. No events were shown on it, even for > enabled calendars. The deleted calendar was on the list of calendars again. > [...]
Similar problem has been detected: Both Calendar and California was running. I added an event in California. In the same moment I clicked "add" I saw the popup that Calendar crashed. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-calendar --gapplication-service crash_function: icaltime_day_of_year executable: /usr/bin/gnome-calendar global_pid: 9932 kernel: 4.7.9-200.fc24.x86_64 package: gnome-calendar-3.20.4-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: gnome-calendar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Hopefully fixed in next release.