Description of problem: I didn't use Evolution, just had it open. I got a reminder popup in gnome-shell for a event I added to evolution's calendar. this crash happened just after delaying the reminder for 1 day. It happened at 00:00 local time. Version-Release number of selected component: evolution-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/evolution/3.10/evolution-alarm-notify crash_function: ptr_array_free executable: /usr/libexec/evolution/3.10/evolution-alarm-notify kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #7 ptr_array_free at garray.c:1082 #8 g_ptr_array_unref at garray.c:1031 #9 gtk_css_computed_values_dispose at gtkcsscomputedvalues.c:49 #11 style_data_unref at gtkstylecontext.c:527 #12 g_hash_table_remove_all_nodes at ghash.c:500 #13 g_hash_table_remove_all at ghash.c:1347 #14 g_hash_table_destroy at ghash.c:1051 #15 gtk_style_context_finalize at gtkstylecontext.c:860 #17 gtk_spin_button_finalize at gtkspinbutton.c:695 #19 gtk_grid_forall at gtkgrid.c:546
Created attachment 846339 [details] File: backtrace
Created attachment 846340 [details] File: cgroup
Created attachment 846341 [details] File: core_backtrace
Created attachment 846342 [details] File: dso_list
Created attachment 846343 [details] File: environ
Created attachment 846344 [details] File: limits
Created attachment 846345 [details] File: maps
Created attachment 846346 [details] File: open_fds
Created attachment 846347 [details] File: proc_pid_status
Created attachment 846348 [details] File: var_log_messages
Thanks for a bug report. There is filled a similar upstream bug [1], thus I'm moving this there. 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=709162
*** Bug 1055305 has been marked as a duplicate of this bug. ***
*** Bug 1065479 has been marked as a duplicate of this bug. ***
*** Bug 1065550 has been marked as a duplicate of this bug. ***