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 599648 - evolution crashed with SIGSEGV in pvl_head()
evolution crashed with SIGSEGV in pvl_head()
Status: RESOLVED DUPLICATE of bug 599627
Product: evolution
Classification: Applications
Component: Tasks
2.28.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-10-26 12:03 UTC by Pedro Villavicencio
Modified: 2009-10-27 03:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Pedro Villavicencio 2009-10-26 12:03:48 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/460054

"Created new memo in Evolution, double-clicked on it, expected it to open; instead, Evolution crashed."

".

Thread 1 (process 6058)

  • #0 pvl_head
    at /build/buildd/libical-0.43/src/libical/pvl.c line 542
  • #1 icalcomponent_free
    at /build/buildd/libical-0.43/src/libical/icalcomponent.c line 259
  • #2 e_cal_model_component_finalize
    at e-cal-model.c line 2473
  • #3 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #4 ecm_append_row
    at e-cal-model.c line 922
  • #5 finish_editing
    at e-table-click-to-add.c line 344
  • #6 item_key_press
    at e-table-click-to-add.c line 323
  • #7 e_marshal_INT__INT_INT_BOXED
    at e-marshal.c line 816
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 ??
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 eti_event
    at e-table-item.c line 2812
  • #13 gnome_canvas_marshal_BOOLEAN__BOXED
    at gnome-canvas-marshal.c line 125
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #18 emit_event
    at e-canvas.c line 250
  • #19 e_canvas_key
    at e-canvas.c line 278
  • #20 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmarshalers.c line 84
  • #21 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #22 ??
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #25 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkwidget.c line 4767
  • #26 IA__gtk_window_propagate_key_event
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkwindow.c line 5144
  • #27 gtk_window_key_press_event
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkwindow.c line 5174
  • #28 bonobo_window_key_press_event
    at bonobo-window.c line 268
  • #29 _gtk_marshal_BOOLEAN__BOXED
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmarshalers.c line 84
  • #30 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #31 ??
    from /usr/lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #34 gtk_widget_event_internal
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkwidget.c line 4767
  • #35 IA__gtk_propagate_event
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c line 2391
  • #36 IA__gtk_main_do_event
    at /build/buildd/gtk+2.0-2.18.3/gtk/gtkmain.c line 1622
  • #37 gdk_event_dispatch
    at /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkevents-x11.c line 2369
  • #38 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #39 ??
    from /lib/libglib-2.0.so.0
  • #40 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #41 bonobo_main
    at bonobo-main.c line 311
  • #42 main
    at main.c line 732

Comment 1 Akhil Laddha 2009-10-27 03:44:14 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 599627 ***