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 257229 - Crash after receiving new mail.
Crash after receiving new mail.
Status: RESOLVED DUPLICATE of bug 252935
Product: GAL
Classification: Deprecated
Component: ETable
unspecified
Other All
: Normal major
: ---
Assigned To: Mike Kestner
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-04-19 15:54 UTC by Dennis Smit
Modified: 2004-04-20 21:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dennis Smit 2004-04-19 15:54:15 UTC
Using evolution 1.5.6, build from CVS daily.

I've been seeing this quite often, after a new mail
has arrived and i click on it evolution crashes.


The following backtrace:

Backtrace was generated from '/opt/gtk2/bin/evolution-1.5'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1097035584 (LWP 1518)]
[New Thread 1171733424 (LWP 32726)]
[Thread debugging using libthread_db enabled]
[New Thread 1097035584 (LWP 1518)]
[New Thread 1171733424 (LWP 32726)]
[Thread debugging using libthread_db enabled]
[New Thread 1097035584 (LWP 1518)]
[New Thread 1171733424 (LWP 32726)]
[New Thread 1163344816 (LWP 32429)]
[New Thread 1154956208 (LWP 32428)]
[New Thread 1146092464 (LWP 32427)]
[New Thread 1136188336 (LWP 1844)]
[New Thread 1127799728 (LWP 1786)]
[New Thread 1118931888 (LWP 1523)]
[New Thread 1110543280 (LWP 1522)]
0x412df411 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

Thread 1 (Thread 1097035584 (LWP 1518))

  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #1 libgnomeui_segv_handle
    at gnome-ui-init.c line 741
  • #2 segv_redirect
    at main.c line 456
  • #3 <signal handler called>
  • #4 eti_ref_at
    at gal-a11y-e-table-item.c line 317
  • #5 atk_table_ref_at
    at atktable.c line 157
  • #6 eti_a11y_cursor_changed_cb
    at gal-a11y-e-table-item.c line 1193
  • #7 e_marshal_VOID__INT_INT
    at e-marshal.c line 812
  • #8 g_closure_invoke
    at gclosure.c line 437
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2436
  • #10 g_signal_emit_valist
  • #11 g_signal_emit
    at gsignal.c line 2239
  • #12 e_selection_model_do_something
    at e-selection-model.c line 449
  • #13 e_selection_model_maybe_do_something
    at e-selection-model.c line 486
  • #14 eti_event
    at e-table-item.c line 145
  • #15 gnome_canvas_marshal_BOOLEAN__BOXED
    at gnome-canvas-marshal.c line 125
  • #16 g_type_class_meta_marshal
    at gclosure.c line 514
  • #17 g_closure_invoke
    at gclosure.c line 437
  • #18 signal_emit_unlocked_R
    at gsignal.c line 2474
  • #19 g_signal_emit_valist
    at gsignal.c line 2205
  • #20 g_signal_emit_by_name
    at gsignal.c line 2263
  • #21 emit_event
    at e-canvas.c line 265
  • #22 e_canvas_button
    at e-canvas.c line 532
  • #23 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #24 g_type_class_meta_marshal
    at gclosure.c line 514
  • #25 g_closure_invoke
    at gclosure.c line 437
  • #26 signal_emit_unlocked_R
    at gsignal.c line 2474
  • #27 g_signal_emit_valist
    at gsignal.c line 2205
  • #28 g_signal_emit
    at gsignal.c line 2239
  • #29 gtk_widget_event_internal
    at gtkwidget.c line 3563
  • #30 gtk_propagate_event
    at gtkmain.c line 2344
  • #31 gtk_main_do_event
    at gtkmain.c line 1582
  • #32 gdk_event_dispatch
    at gdkevents-x11.c line 2152
  • #33 g_main_dispatch
    at gmain.c line 1942
  • #34 g_main_context_dispatch
    at gmain.c line 2492
  • #35 g_main_context_iterate
    at gmain.c line 2573
  • #36 g_main_loop_run
    at gmain.c line 2777
  • #37 bonobo_main
    at bonobo-main.c line 297
  • #38 main
    at main.c line 600
  • #0 __waitpid_nocancel
    from /lib/tls/libpthread.so.0

Comment 1 Jeffrey Stedfast 2004-04-19 16:03:18 UTC
this is probably that Atk bug that Sun China has been trying to fix as
of late.
Comment 2 Gerardo Marin 2004-04-20 21:39:03 UTC

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