Description of problem: Iād added a CalDAV calendar, let it sync, confirmed that it worked, and then removed the newly added calendar. Then I left the computer alone for 15 minutes. When I got back, California had crashed. Version-Release number of selected component: california-0.4.0-4.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: california crash_function: california_view_week_day_pane_restack_events executable: /usr/bin/california global_pid: 32450 kernel: 4.3.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 california_view_week_day_pane_restack_events at /usr/src/debug/california-0.4.0/src/view/week/week-day-pane.vala:39 #6 california_view_week_day_pane_real_add_event at /usr/src/debug/california-0.4.0/src/view/week/week-day-pane.vala:197 #7 california_view_week_grid_on_calendar_instance_added_or_altered at /usr/src/debug/california-0.4.0/src/view/week/week-grid.vala:315 #8 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102 #9 _g_closure_invoke_va at gclosure.c:864 #11 g_signal_emit_by_name at gsignal.c:3479 #12 g_cclosure_marshal_VOID__OBJECTv at gmarshal.c:2102 #13 _g_closure_invoke_va at gclosure.c:864 #15 g_signal_emit_by_name at gsignal.c:3479 #16 _california_backing_eds_calendar_source_subscription_on_objects_modified_e_cal_client_view_objects_modified at /usr/src/debug/california-0.4.0/src/backing/eds/backing-eds-calendar-source-subscription.vala:277
Created attachment 1130164 [details] File: backtrace
Created attachment 1130165 [details] File: cgroup
Created attachment 1130166 [details] File: core_backtrace
Created attachment 1130167 [details] File: dso_list
Created attachment 1130168 [details] File: environ
Created attachment 1130169 [details] File: limits
Created attachment 1130170 [details] File: maps
Created attachment 1130171 [details] File: mountinfo
Created attachment 1130172 [details] File: namespaces
Created attachment 1130173 [details] File: open_fds
Created attachment 1130174 [details] File: proc_pid_status
Created attachment 1130175 [details] File: var_log_messages
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.