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 332693 - Evolution crash on starting calendar
Evolution crash on starting calendar
Status: RESOLVED DUPLICATE of bug 329866
Product: evolution
Classification: Applications
Component: Calendar
2.4.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-02-27 01:11 UTC by rob
Modified: 2006-07-11 00:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description rob 2006-02-27 01:11:46 UTC
Distribution: Debian testing/unstable
Package: Evolution
Severity: blocker
Version: GNOME2.12.2 2.4.x
Gnome-Distributor: Debian
Synopsis: Evolution crash on starting calendar
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.4.x
BugBuddy-GnomeVersion: 2.0 (2.12.1)
Description:
Description of the crash:

Evolution segfaults when I try to run the calendar

Steps to reproduce the crash:
1.  Start evolution
2.  Click on 'Calendars'
3.  Boom!

Expected Results:
Calendar should start

How often does this happen?
Every time

Additional Information:
Deleteing all files under /home/rob/.evolution/calendar/ has no effect
Deleting gconf node has no effect (including restartin gconfd)
Can sometimes view forward a few days, but attempts to go back or view
Todays or Tomorrows events cause the crash





Debugging Information:

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1230804768 (LWP 19560)]
[New Thread -1313866832 (LWP 19585)]
[New Thread -1286603856 (LWP 19580)]
[New Thread -1295520848 (LWP 19573)]
[New Thread -1274020944 (LWP 19570)]
[New Thread -1264546896 (LWP 19569)]
[New Thread -1255146576 (LWP 19567)]
[New Thread -1244394576 (LWP 19566)]
[New Thread -1235612752 (LWP 19564)]
(no debugging symbols found)
0xb74d8231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread -1230804768 (LWP 19560))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 es_menu_hook_get_type
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/libc.so.6
  • #5 e_cal_resolve_tzid_cb
    from /usr/lib/libecal-1.2.so.3
  • #6 e_cal_generate_instances_for_object
    from /usr/lib/libecal-1.2.so.3
  • #7 e_cal_model_get_client_for_uri
    from /usr/lib/evolution/2.4/components/libevolution-calendar.so
  • #8 g_cclosure_marshal_VOID__POINTER
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 e_cal_view_get_type
    from /usr/lib/libecal-1.2.so.3
  • #14 g_cclosure_marshal_VOID__POINTER
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #19 e_cal_view_listener_get_type
    from /usr/lib/libecal-1.2.so.3
  • #20 _ORBIT_skel_small_GNOME_Evolution_Calendar_CalViewListener_notifyObjectsAdded
    from /usr/lib/libecal-1.2.so.3
  • #21 ORBit_POA_setup_root
    from /usr/lib/libORBit-2.so.0
  • #22 ORBit_OAObject_invoke
    from /usr/lib/libORBit-2.so.0
  • #23 ORBit_small_invoke_adaptor
    from /usr/lib/libORBit-2.so.0
  • #24 ORBit_POAObject_post_invoke
    from /usr/lib/libORBit-2.so.0
  • #25 ORBit_POAObject_post_invoke
    from /usr/lib/libORBit-2.so.0
  • #26 giop_thread_queue_process
    from /usr/lib/libORBit-2.so.0
  • #27 giop_recv_buffer_get
    from /usr/lib/libORBit-2.so.0
  • #28 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #29 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #30 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #31 ConfigDatabase_set
    from /usr/lib/libgconf-2.so.4
  • #32 gconf_engine_set
    from /usr/lib/libgconf-2.so.4
  • #33 gconf_engine_set
    from /usr/lib/libgconf-2.so.4
  • #34 gconf_client_set_string
    from /usr/lib/libgconf-2.so.4
  • #35 e_shell_window_get_type
  • #36 e_shell_window_get_type
  • #37 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #38 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #39 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #40 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #42 e_sidebar_get_type
  • #43 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #44 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #45 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #46 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #47 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #48 gtk_toggle_button_toggled
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 gtk_toggle_button_set_inconsistent
    from /usr/lib/libgtk-x11-2.0.so.0
  • #50 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #51 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #52 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #53 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #54 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #55 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #56 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #57 gtk_toggle_button_set_inconsistent
    from /usr/lib/libgtk-x11-2.0.so.0
  • #58 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #59 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #60 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #61 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #62 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #63 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #64 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #65 _gtk_button_paint
    from /usr/lib/libgtk-x11-2.0.so.0
  • #66 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #67 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #68 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #69 g_signal_stop_emission
    from /usr/lib/libgobject-2.0.so.0
  • #70 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #71 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #72 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #73 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #74 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #75 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #76 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #77 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #78 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #79 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #80 main
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0




------- Bug created by bug-buddy at 2006-02-27 01:11 -------

Comment 1 Chenthill P 2006-03-10 06:35:04 UTC
What is the timezone being used ?
Comment 2 rob 2006-03-12 22:58:14 UTC
Time zone: Australia/Sydney

Problem now only occurs when I go back to the days in question (Monday & Tuesday of the week before last).

This means that the bug is likely being triggered by bad events for one of those days - where can I get this to provide it?
Comment 3 Poornima 2006-05-06 07:11:26 UTC
If debug rpms of evolution is installed and then try out this scenario you can make out if any events is causing this crash. Update this bug with those stack traces 
Comment 4 André Klapper 2006-07-11 00:14:14 UTC
Poornima: Not this way.
Comment 5 André Klapper 2006-07-11 00:15:13 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 is fixed in Evolution 2.6.

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