Version-Release number of selected component: evolution-data-server-3.12.5-3.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: g_mutex_clear executable: /usr/libexec/evolution-calendar-factory kernel: 3.16.1-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 g_mutex_clear at gthread-posix.c:1295 #3 cal_backend_finalize at e-cal-backend.c:639 #5 data_cal_view_dispose at e-data-cal-view.c:435 #7 e_cal_backend_remove_view at e-cal-backend.c:1440 #8 impl_DataCalView_dispose at e-data-cal-view.c:267 #9 ffi_call_unix64 at ../src/x86/unix64.S:76 #10 ffi_call at ../src/x86/ffi64.c:525 #11 g_cclosure_marshal_generic at gclosure.c:1448 #16 e_gdbus_stub_handle_method_call at e-gdbus-templates.c:678 #17 call_in_idle_cb at gdbusconnection.c:4884
Created attachment 934005 [details] File: backtrace
Created attachment 934006 [details] File: cgroup
Created attachment 934007 [details] File: core_backtrace
Created attachment 934008 [details] File: dso_list
Created attachment 934009 [details] File: environ
Created attachment 934010 [details] File: limits
Created attachment 934011 [details] File: maps
Created attachment 934012 [details] File: open_fds
Created attachment 934013 [details] File: proc_pid_status
Created attachment 934014 [details] File: var_log_messages
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions. [1] https://bugzilla.gnome.org/show_bug.cgi?id=736006
*** Bug 1163373 has been marked as a duplicate of this bug. ***
*** Bug 1171453 has been marked as a duplicate of this bug. ***
mcrha - I see an eds commit referencing https://bugzilla.gnome.org/show_bug.cgi?id=701138 is in 3.12.9 which is pending for F21, but I'm not sure whether libical also needs to be changed to fix this. It's high up on the list of common F21 crashes, so it'd be good to have it fixed if possible. Will the new e-d-s fix it when it goes stable, or do we need libical changes too?
I do not know for sure how much the libical changes are related to the crash (or basically any other involving libical and timezone lookup or recurrence unwinding). I hoped that the libical mailing list post [1] will receive some attention during the last few weeks, like after they'll approve it I would include it in Fedora's libical, but they are quiet. I do not think the libical change it wrong, at least my tests didn't spot any issue, but it still felt like a better choice to wait for the upstream opinion on the change. It did feel like that. I will provide an update of libical with the proposed change and let's see whether my tests were correct. As for example bug #1176204 looks more accurate for the libical part of the bug, I'll use rather it, than this bug report, which I'd like to keep in evolution-data-server. [1] https://bugzilla.gnome.org/show_bug.cgi?id=701138#c23
*** Bug 1176375 has been marked as a duplicate of this bug. ***
*** Bug 1178019 has been marked as a duplicate of this bug. ***