GNOME Bugzilla – Bug 592343
Crashes when attempt to create recurring event.
Last modified: 2009-08-22 03:35:29 UTC
Created attachment 141158 [details] gdb crash report Crashes when attempt to create recurring event. Steps to repeat: 1/Launch Evolution. 2/Select Calendar. 3/Create new event. 4/Open event. 5/Select Recurrence. 6/Define recurrence. 7/Close recurrence. 8/Save event. 9/Crash occurs. (On relaunch original event is there. Recurrence is not.)
Seems to work fine here in 2.27.90. Pasting traces from attached crash report (evolution:22573): calendar-gui-CRITICAL **: simple_recur_to_comp: assertion `GTK_BIN (priv->special)->child != NULL' failed (evolution:22573): Gtk-CRITICAL **: gtk_widget_get_toplevel: assertion `GTK_IS_WIDGET (widget)' failed (evolution:22573): Gtk-CRITICAL **: gtk_widget_get_toplevel: assertion `GTK_IS_WIDGET (widget)' failed (evolution:22573): calendar-gui-CRITICAL **: simple_recur_to_comp: assertion `priv->ending_date_edit != NULL' failed (evolution:22573): e-dateedit.c-CRITICAL **: e_date_edit_get_date: assertion `E_IS_DATE_EDIT (dedit)' failed (evolution:22573): Gtk-CRITICAL **: gtk_widget_get_toplevel: assertion `GTK_IS_WIDGET (widget)' failed (evolution:22573): Gtk-CRITICAL **: gtk_widget_get_toplevel: assertion `GTK_IS_WIDGET (widget)' failed (evolution:22573): Gtk-CRITICAL **: gtk_widget_get_toplevel: assertion `GTK_IS_WIDGET (widget)' failed [New Thread 0x7ffa15b62950 (LWP 22619)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffa1c0af7f0 (LWP 22573)] 0x00007ffa19c67316 in comp_util_sanitize_recurrence_master (comp=0x11ef320, client=0x1067ee0) at comp-util.c:823 823 comp-util.c: No such file or directory. in comp-util.c (gdb) thread apply all bt
+ Trace 217024
Thread 22 (Thread 0x7ffa15b62950 (LWP 22619))
Thread 1 (Thread 0x7ffa1c0af7f0 (LWP 22573))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. 2.26.3.xx *** This bug has been marked as a duplicate of bug 579779 ***