Bug 383714 – crash in Evolution: just closing the program...

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 383714 - crash in Evolution: just closing the program...


Summary:	crash in Evolution: just closing the program...


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 13:05 UTC by richard.c.mcintosh
Modified:	2006-12-09 11:15 UTC

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

Description richard.c.mcintosh 2006-12-08 13:05:13 UTC

What were you doing when the application crashed?
just closing the program. 


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

Memory status: size: 222593024 vsize: 0 resident: 222593024 share: 0 rss: 20803584 rss_rlim: 0
CPU usage: start_time: 1165576947 rtime: 0 utime: 580 stime: 0 cutime:514 cstime: 0 timeout: 66 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232877904 (LWP 5118)]
[New Thread -1389679712 (LWP 5301)]
[New Thread -1343353952 (LWP 5165)]
[New Thread -1325786208 (LWP 5148)]
[New Thread -1317000288 (LWP 5147)]
[New Thread -1272693856 (LWP 5142)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 92556

Thread 4 (Thread -1325786208 (LWP 5148))

#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 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#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 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#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_store_sync
from /usr/lib/libcamel-provider-1.2.so.8
#25 camel_store_sync
from /usr/lib/libcamel-provider-1.2.so.8
#26 mail_empty_trash
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#27 mail_enable_stop
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#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 Christian Kirbach 2006-12-09 11:15:43 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 348149 ***