Bug 380717 – crash in Evolution: Clicked on a mail to rea...

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 380717 - crash in Evolution: Clicked on a mail to rea...


Summary:	crash in Evolution: Clicked on a mail to rea...


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-30 00:40 UTC by Daniel.J.Larsson
Modified:	2006-11-30 01:43 UTC

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

Description Daniel.J.Larsson 2006-11-30 00:40:54 UTC

What were you doing when the application crashed?
Clicked on a mail to read it


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

Memory status: size: 157663232 vsize: 0 resident: 157663232 share: 0 rss: 46305280 rss_rlim: 0
CPU usage: start_time: 1164837860 rtime: 0 utime: 6671 stime: 0 cutime:5851 cstime: 0 timeout: 820 it_real_value: 0 frequency: 2

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232755024 (LWP 26754)]
[New Thread -1309852768 (LWP 26781)]
[New Thread -1300767840 (LWP 26772)]
[New Thread -1278063712 (LWP 26771)]
[New Thread -1269658720 (LWP 26766)]
[New Thread -1260872800 (LWP 26765)]
[New Thread -1252480096 (LWP 26763)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 90430

Thread 1 (Thread -1232755024 (LWP 26754))

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

Comment 1 André Klapper 2006-11-30 01:43:20 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 ***