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 274503 - Evolution crashed in deleting stale account displayed in 'tasks'
Evolution crashed in deleting stale account displayed in 'tasks'
Status: RESOLVED DUPLICATE of bug 224322
Product: evolution
Classification: Applications
Component: Shell
2.2.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-04-08 08:24 UTC by Poornima
Modified: 2013-09-10 14:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Poornima 2005-04-08 08:24:32 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. To reproduce bug 273964 was trying to modify old appointments in exchange
'calendar'.
2. Then went to 'Task' component, observed old account which was removed
still displayed.
3. Launched gconf-editor, removed that account from tasks, as it was only
displayed under 'Tasks'. After removing it observed evolution crashed.

Stack traces show only html_* api's , so set component as shell, not very
sure of component
Actual Results:


Expected Results:


How often does this happen? 
Not reproducible again

Additional Information:

Backtrace was generated from '/opt/gnome/bin/evolution'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1095049728 (LWP 24432)]
[New Thread 1114987440 (LWP 25093)]
[Thread debugging using libthread_db enabled]
[New Thread 1095049728 (LWP 24432)]
[New Thread 1114987440 (LWP 25093)]
[Thread debugging using libthread_db enabled]
[New Thread 1095049728 (LWP 24432)]
[New Thread 1114987440 (LWP 25093)]
[New Thread 1123031984 (LWP 25092)]
[New Thread 1125133232 (LWP 25091)]
[New Thread 1117088688 (LWP 25032)]
[New Thread 1110784944 (LWP 25026)]
[New Thread 1108679600 (LWP 24469)]
0xffffe410 in ?? ()

Thread 1 (Thread 1095049728 (LWP 24432))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    from /opt/gnome/lib/libgnomeui-2.so.0
  • #6 segv_redirect
    at main.c line 428
  • #7 <signal handler called>
  • #8 html_object_is_container
    at htmlobject.c line 1314
  • #9 html_point_to_leaf
    at htmlinterval.c line 254
  • #10 html_interval_flat
    at htmlinterval.c line 276
  • #11 html_interval_unselect
    at htmlinterval.c line 184
  • #12 html_engine_redraw_selection
    at htmlengine.c line 6121
  • #13 html_engine_set_focus
    at htmlengine.c line 5192
  • #14 focus_in_event
    at gtkhtml.c line 1843
  • #15 _gtk_marshal_BOOLEAN__BOXED
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #16 g_type_class_meta_marshal
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #17 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #18 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #21 gtk_widget_event_internal
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #22 do_focus_change
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #23 _gtk_window_set_is_active
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #24 gtk_window_focus_in_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #25 _gtk_marshal_BOOLEAN__BOXED
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #26 g_type_class_meta_marshal
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #27 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #28 signal_emit_unlocked_R
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #31 gtk_widget_event_internal
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #32 gtk_main_do_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #33 gdk_event_dispatch
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #34 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #35 g_main_context_iterate
    from /opt/gnome/lib/libglib-2.0.so.0
  • #36 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #37 bonobo_main
    from /opt/gnome/lib/libbonobo-2.so.0
  • #38 main
    at main.c line 610
  • #0 ??

Comment 1 Elijah Newren 2005-04-10 03:00:45 UTC
Looks similar to the stack trace in bug 224322, though that was with an older
version and it was closed believing it had been fixed...
Comment 2 Nagappan Alagappan 2005-07-21 12:47:49 UTC
Elijah: Yes you are right, both the stack trace are similar.

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