Bug 648453 – crash in Evolution: Sending mail most probab...

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 648453 - crash in Evolution: Sending mail most probab...


Summary:	crash in Evolution: Sending mail most probab...


Status:	RESOLVED DUPLICATE of bug 577627

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.32.x (obsolete)
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-04-22 09:58 UTC by Olivier Berger
Modified:	2011-04-23 12:18 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description Olivier Berger 2011-04-22 09:58:33 UTC

What were you doing when the application crashed?
Sending mail most probably...


Distribution: Debian wheezy/sid
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10905000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 376537088 vsize: 376537088 resident: 257638400 share: 23990272 rss: 257638400 rss_rlim: 18446744073709551615
CPU usage: start_time: 1303460751 rtime: 66542 utime: 61559 stime: 4983 cutime:85 cstime: 122 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xa3dfdb70 (LWP 5987)]
[New Thread 0xa4dffb70 (LWP 5954)]
[New Thread 0xb2beab70 (LWP 3935)]
[New Thread 0xb33ebb70 (LWP 3934)]
[New Thread 0xb3f06b70 (LWP 3932)]
[New Thread 0xb4707b70 (LWP 3931)]
[New Thread 0xb52cdb70 (LWP 3930)]
0xb682ea71 in ?? () from /usr/lib/libsqlite3.so.0

+ Trace 226842

Thread 3 (Thread 0xa4dffb70 (LWP 5954))

#0 __kernel_vsyscall
#1 waitpid
at ../sysdeps/unix/syscall-template.S line 82
#2 g_spawn_sync
at /build/buildd-glib2.0_2.28.4-1-i386-nLAaCs/glib2.0-2.28.4/./glib/gspawn.c line 392
#3 g_spawn_command_line_sync
at /build/buildd-glib2.0_2.28.4-1-i386-nLAaCs/glib2.0-2.28.4/./glib/gspawn.c line 706
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 segv_redirect
at main.c line 283
#6 <signal handler called>
#7 camel_partition_table_lookup
at camel-partition-table.c line 299
#8 text_index_add_name_to_word
at camel-text-index.c line 250
#9 hash_write_word
at camel-text-index.c line 711
#10 g_hash_table_foreach
at /build/buildd-glib2.0_2.28.4-1-i386-nLAaCs/glib2.0-2.28.4/./glib/ghash.c line 1330
#11 text_index_write_name
at camel-text-index.c line 724
#12 camel_index_write_name
at camel-index.c line 240
#13 camel_folder_summary_info_new_from_parser
at camel-folder-summary.c line 2710
#14 camel_folder_summary_add_from_parser
at camel-folder-summary.c line 2602
#15 summary_update
at camel-mbox-summary.c line 520
#16 mbox_summary_check
at camel-mbox-summary.c line 645
#17 camel_local_summary_check
at camel-local-summary.c line 277
#18 mbox_summary_sync
at camel-mbox-summary.c line 976
#19 camel_local_summary_sync
at camel-local-summary.c line 313
#20 local_sync
at camel-local-folder.c line 535
#21 camel_folder_sync
at camel-folder.c line 1124
#22 send_queue_exec
at mail-ops.c line 849
#23 mail_msg_proxy
at mail-mt.c line 469
#24 g_thread_pool_thread_proxy
at /build/buildd-glib2.0_2.28.4-1-i386-nLAaCs/glib2.0-2.28.4/./glib/gthreadpool.c line 319
#25 g_thread_create_proxy
at /build/buildd-glib2.0_2.28.4-1-i386-nLAaCs/glib2.0-2.28.4/./glib/gthread.c line 1897
#26 start_thread
at pthread_create.c line 300
#27 clone
at ../sysdeps/unix/sysv/linux/i386/clone.S line 130


	Inferior 1 [process 3928] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** evolution-mail **: cmp_array_uids: assertion `md1->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md2->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md1->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md2->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md1->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md2->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md1->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md1->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md1->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md1->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md2->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md2->mi != NULL' failed 
** evolution-mail **: cmp_array_uids: assertion `md2->mi != NULL' failed 
** camel **: camel_folder_free_message_info: assertion `info != NULL' failed 
** camel **: camel_folder_free_message_info: assertion `info != NULL' failed 


----------- .xsession-errors (6 sec old) ---------------------
(evolution:3928): camel-WARNING **: Could not find key entry for word '000000000': Succès
(evolution:3928): camel-WARNING **: Could not find key entry for word '20fdf1f2878098951ba45492415e24bded': Succès
(evolution:3928): camel-WARNING **: Could not find key entry for word '2018673fc9e82bac0b185d460e2d234662': Succès
(evolution:3928): camel-WARNING **: Could not find key entry for word '2018673fc9e82bac0b185d460e2d234662': Succès
(evolution:3928): camel-local-provider-WARNING **: The next message didn't start where I expected, building summary from start
--------------------------------------------------

Comment 1 Akhil Laddha 2011-04-23 12:18:50 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 bug 577627 ***