Bug 371963 – crash in Evolution: Clicked on an email in I...

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 371963 - crash in Evolution: Clicked on an email in I...


Summary:	crash in Evolution: Clicked on an email in I...


Status:	RESOLVED DUPLICATE of bug 330728

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-07 12:00 UTC by numpty
Modified:	2006-11-07 19:52 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description numpty 2006-11-07 12:00:47 UTC

What were you doing when the application crashed?
Clicked on an email in Inbox


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 59772928 vsize: 0 resident: 203120640 share: 0 rss: 203120640 rss_rlim: 0
CPU usage: start_time: 182 rtime: 0 utime: 1162896645 stime: 0 cutime:20810 cstime: 0 timeout: 19938 it_real_value: 0 frequency: 872

Backtrace was generated from '/usr/X11R6/bin//evolution-2.8'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 805606576 (LWP 5247)]
[New Thread 900723952 (LWP 18480)]
[New Thread 870204656 (LWP 5267)]
[New Thread 866563312 (LWP 5264)]
[New Thread 858174704 (LWP 5262)]
[New Thread 849786096 (LWP 5259)]
[New Thread 839111920 (LWP 5257)]
[New Thread 830321904 (LWP 5255)]
[New Thread 821933296 (LWP 5252)]
0x0ea1f220 in waitpid () from /lib/libc.so.6

+ Trace 83948

Thread 1 (Thread 805606576 (LWP 5247))

#0 waitpid
from /lib/libc.so.6
#1 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 segv_redirect
at main.c line 426
#3 <signal handler called>
#4 ect_check
at gal-a11y-e-cell-text.c line 69
#5 ect_get_name
at gal-a11y-e-cell-text.c line 81
#6 atk_object_get_name
from /usr/lib/libatk-1.0.so.0
#7 gnome_accessibility_module_shutdown
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#8 gnome_accessibility_module_shutdown
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#9 signal_emit_unlocked_R
at gsignal.c line 2406
#10 IA__g_signal_emit_valist
at gsignal.c line 2199
#11 IA__g_signal_emit
at gsignal.c line 2243
#12 atk_object_notify_state_change
from /usr/lib/libatk-1.0.so.0
#13 gal_a11y_e_cell_add_state
at gal-a11y-e-cell.c line 496
#14 ectr_model_row_changed_cb
at gal-a11y-e-cell-tree.c line 46
#15 IA__g_cclosure_marshal_VOID__INT
at gmarshal.c line 216
#16 IA__g_closure_invoke
at gclosure.c line 490
#17 signal_emit_unlocked_R
at gsignal.c line 2440
#18 IA__g_signal_emit_valist
at gsignal.c line 2199
#19 IA__g_signal_emit
at gsignal.c line 2243
#20 e_table_model_row_changed
at e-table-model.c line 487
#21 etta_proxy_node_data_changed
at e-tree-table-adapter.c line 777
#22 IA__g_cclosure_marshal_VOID__POINTER
at gmarshal.c line 601
#23 IA__g_closure_invoke
at gclosure.c line 490
#24 signal_emit_unlocked_R
at gsignal.c line 2440
#25 IA__g_signal_emit_valist
at gsignal.c line 2199
#26 IA__g_signal_emit
at gsignal.c line 2243
#27 e_tree_model_node_data_changed
at e-tree-model.c line 279
#28 main_folder_changed
at message-list.c line 2964
#29 do_async_event
at mail-mt.c line 676
#30 idle_async_event
at mail-mt.c line 687
#31 g_idle_dispatch
at gmain.c line 3926
#32 IA__g_main_context_dispatch
at gmain.c line 2045
#33 g_main_context_iterate
at gmain.c line 2677
#34 IA__g_main_loop_run
at gmain.c line 2881
#35 bonobo_main
from /usr/lib/libbonobo-2.so.0
#36 main
at main.c line 615
#0 waitpid
from /lib/libc.so.6

Comment 1 Karsten Bräckelmann 2006-11-07 19:52:54 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 330728 ***