Bug 383747 – 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 383747 - crash in Evolution:


Summary:	crash in Evolution:


Status:	RESOLVED DUPLICATE of bug 348149

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-12-08 14:49 UTC by mattioni.filippo
Modified:	2007-01-17 17:05 UTC

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

Description mattioni.filippo 2006-12-08 14:49:37 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: 223936512 vsize: 0 resident: 223936512 share: 0 rss: 52482048 rss_rlim: 0
CPU usage: start_time: 1165567182 rtime: 0 utime: 379 stime: 0 cutime:334 cstime: 0 timeout: 45 it_real_value: 0 frequency: 0

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 -1233062224 (LWP 25494)]
[New Thread -1372791904 (LWP 25544)]
[New Thread -1364399200 (LWP 25537)]
[New Thread -1356006496 (LWP 25509)]
[New Thread -1294890080 (LWP 25503)]
[New Thread -1285743712 (LWP 25501)]
[New Thread -1277314144 (LWP 25498)]
[New Thread -1268884576 (LWP 25497)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 92580

Thread 8 (Thread -1268884576 (LWP 25497))

#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 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 IA__g_logv
#8 IA__g_log
#9 IA__g_assert_warning
at gmessages.c line 552
#10 camel_key_table_lookup
from /usr/lib/libcamel-1.2.so.8
#11 camel_text_index_new
from /usr/lib/libcamel-1.2.so.8
#12 IA__g_hash_table_foreach
at ghash.c line 662
#13 camel_text_index_new
from /usr/lib/libcamel-1.2.so.8
#14 camel_index_write_name
from /usr/lib/libcamel-1.2.so.8
#15 camel_folder_summary_info_new_from_parser
from /usr/lib/libcamel-provider-1.2.so.8
#16 camel_folder_summary_add_from_parser
from /usr/lib/libcamel-provider-1.2.so.8
#17 camel_mbox_summary_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
#18 camel_mbox_summary_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
#19 camel_local_summary_check
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
#20 camel_mbox_summary_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
#21 camel_local_summary_sync
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
#22 camel_local_folder_construct
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
#23 camel_folder_sync
from /usr/lib/libcamel-provider-1.2.so.8
#24 camel_filter_driver_filter_folder
from /usr/lib/libcamel-provider-1.2.so.8
#25 em_filter_folder_element_filter
at mail-ops.c line 140
#26 fetch_mail_fetch
at mail-ops.c line 325
#27 mail_msg_received
at mail-mt.c line 570
#28 e_msgport_reply
from /usr/lib/libedataserver-1.2.so.7
#29 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#30 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 Kjartan Maraas 2007-01-16 09:40:43 UTC

Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug.

Comment 2 palfrey 2007-01-17 17:05:33 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 348149 ***