Bug 517625 – Evolution crashed : just after creating an appointment

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 517625 - Evolution crashed : just after creating an appointment


Summary:	Evolution crashed : just after creating an appointment


Status:	RESOLVED OBSOLETE

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	2.22.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-20 10:27 UTC by Akhil Laddha
Modified:	2010-09-14 09:08 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description Akhil Laddha 2008-02-20 10:27:15 UTC

Evolution 2.21.92

Evolution with exchange backend

Gdb traces of evolution process

(evolution:4190): libecal-CRITICAL **: e_cal_component_get_vtype: assertion `priv->icalcomp != NULL' failed
calendar-gui-Message: make_title_from_comp(): Cannot handle object of type 0

(evolution:4190): libecal-CRITICAL **: e_cal_component_get_vtype: assertion `priv->icalcomp != NULL' failed

(evolution:4190): libecal-CRITICAL **: e_cal_component_get_uid: assertion `priv->icalcomp != NULL' failed

(evolution:4190): libecal-CRITICAL **: e_cal_component_get_summary: assertion `priv->icalcomp != NULL' failed

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb66e5a80 (LWP 4190)]
0xb677ff73 in strlen () from /lib/libc.so.6
(gdb) thread apply all bt

+ Trace 189841

Thread 1 (Thread 0xb66e5a80 (LWP 4190))

#0 strlen
from /lib/libc.so.6
#1 e_dialog_editable_set
at e-dialog-widgets.c line 267
#2 event_page_fill_widgets
at event-page.c line 1024
#3 comp_editor_page_fill_widgets
at comp-editor-page.c line 264
#4 real_edit_comp
at comp-editor.c line 2468
#5 event_editor_edit_comp
at event-editor.c line 690
#6 comp_editor_edit_comp
at comp-editor.c line 2681
#7 open_event_with_flags
at e-calendar-view.c line 1990
#8 e_day_view_on_event_double_click
at e-day-view.c line 4157
#9 e_day_view_on_main_canvas_button_press
at e-day-view.c line 3765
#10 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 84
#11 g_closure_invoke
at gclosure.c line 490
#12 signal_emit_unlocked_R
at gsignal.c line 2440
#13 g_signal_emit_valist
at gsignal.c line 2209
#14 g_signal_emit
at gsignal.c line 2243
#15 gtk_widget_event_internal
at gtkwidget.c line 4678
#16 gtk_propagate_event
at gtkmain.c line 2336
#17 gtk_main_do_event
at gtkmain.c line 1556
#18 gdk_event_dispatch
at gdkevents-x11.c line 2351
#19 g_main_context_dispatch
at gmain.c line 2064
#20 g_main_context_iterate
at gmain.c line 2697
#21 g_main_loop_run
at gmain.c line 2905
#22 bonobo_main
at bonobo-main.c line 311
#23 main
at main.c line 721

Comment 1 Matthew Barnes 2008-03-11 00:34:26 UTC

Bumping version to a stable release.

Comment 2 Milan Crha 2008-09-16 12:37:39 UTC

I believe this will do things in a different way when running on 2.23.92+, where Chen changed the ECalModel.

Comment 3 Nick Jenkins 2009-01-08 23:35:39 UTC

Also seems to be logged downstream as: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/299021 - that bug has various automated attachments to assist with debugging, but from the "ThreadStacktrace.txt" attachment, the "Thread 1 (process 10019):" section looks very similar to the Gdb trace above, just with more numbers and stuff after each line.

Comment 4 Milan Crha 2009-01-09 11:22:31 UTC

You've right, it seems like the same issue, on Evolution 2.22.3.1.