Bug 366524 – crash in Evolution: Just opening 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 366524 - crash in Evolution: Just opening program


Summary:	crash in Evolution: Just opening 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-10-28 21:50 UTC by daniel
Modified:	2006-10-28 22:32 UTC

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

Description daniel 2006-10-28 21:50:33 UTC

What were you doing when the application crashed?
Just opening program


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

Memory status: size: 166555648 vsize: 0 resident: 166555648 share: 0 rss: 31457280 rss_rlim: 0
CPU usage: start_time: 1162072106 rtime: 0 utime: 411 stime: 0 cutime:314 cstime: 0 timeout: 97 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 -1232648528 (LWP 5413)]
[New Thread -1343837280 (LWP 5438)]
[New Thread -1353028704 (LWP 5432)]
[New Thread -1344636000 (LWP 5431)]
[New Thread -1335444576 (LWP 5430)]
[New Thread -1317430368 (LWP 5425)]
[New Thread -1309037664 (LWP 5424)]
[New Thread -1275073632 (LWP 5419)]
[New Thread -1266680928 (LWP 5418)]
[New Thread -1257088096 (LWP 5417)]
[New Thread -1248695392 (LWP 5416)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 79470

Thread 9 (Thread -1266680928 (LWP 5418))

#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_message
from /usr/lib/libcamel-provider-1.2.so.8
#16 camel_folder_summary_add_from_message
from /usr/lib/libcamel-provider-1.2.so.8
#17 camel_local_summary_get_type
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_add
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
#20 camel_mbox_folder_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
#21 camel_folder_append_message
from /usr/lib/libcamel-provider-1.2.so.8
#22 camel_filter_driver_filter_message
from /usr/lib/libcamel-provider-1.2.so.8
#23 camel_filter_driver_filter_folder
from /usr/lib/libcamel-provider-1.2.so.8
#24 mail_fetch_mail
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#25 mail_fetch_mail
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#26 mail_enable_stop
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#27 e_msgport_reply
from /usr/lib/libedataserver-1.2.so.7
#28 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#29 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 Karsten Bräckelmann 2006-10-28 22:32:37 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 ***