Bug 397281 – crash in Evolution:

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 397281 - crash in Evolution:


Summary:	crash in Evolution:


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:	2007-01-16 15:09 UTC by polyformal
Modified:	2007-01-16 15:34 UTC

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

Description polyformal 2007-01-16 15:09:50 UTC

What were you doing when the application crashed?



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

Memory status: size: 225292288 vsize: 0 resident: 225292288 share: 0 rss: 56262656 rss_rlim: 0
CPU usage: start_time: 1168849768 rtime: 0 utime: 45750 stime: 0 cutime:42209 cstime: 0 timeout: 3541 it_real_value: 0 frequency: 42

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 -1232836944 (LWP 6229)]
[New Thread -1327506528 (LWP 14743)]
[New Thread -1303794784 (LWP 8210)]
[New Thread -1294992480 (LWP 6246)]
[New Thread -1284645984 (LWP 6243)]
[New Thread -1266136160 (LWP 6241)]
[New Thread -1257743456 (LWP 6239)]
[New Thread -1248957536 (LWP 6233)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 102708

Thread 1 (Thread -1232836944 (LWP 6229))

#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 g_signal_chain_from_overridden
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 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 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#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 g_cclosure_marshal_VOID__POINTER
from /usr/lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#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 mail_msgport_received
at mail-mt.c line 488
#32 g_io_channel_unix_get_fd
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#34 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#35 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#36 bonobo_main
from /usr/lib/libbonobo-2.so.0
#37 main
at main.c line 615
#0 __kernel_vsyscall

Comment 1 Kjartan Maraas 2007-01-16 15:34:38 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 ***