Bug 392244 – crash in Evolution: receiving/sending messag...

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 392244 - crash in Evolution: receiving/sending messag...


Summary:	crash in Evolution: receiving/sending messag...


Status:	RESOLVED DUPLICATE of bug 352284

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-03 10:55 UTC by emelinepeyrat
Modified:	2007-01-03 18:23 UTC

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

Description emelinepeyrat 2007-01-03 10:55:39 UTC

What were you doing when the application crashed?
receiving/sending messages
it crashed during the receiving part
my account is well configured (pop and smtp)

this is not the first time


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

Memory status: size: 1784135680 vsize: 0 resident: 1784135680 share: 0 rss: 658927616 rss_rlim: 0
CPU usage: start_time: 1167821513 rtime: 0 utime: 2082 stime: 0 cutime:1508 cstime: 0 timeout: 574 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 -1233430864 (LWP 4818)]
[New Thread -1301460064 (LWP 4848)]
[New Thread -1293067360 (LWP 4835)]
[New Thread -1292801120 (LWP 4831)]
[New Thread -1284408416 (LWP 4830)]
[New Thread -1256875104 (LWP 4829)]
[New Thread -1265267808 (LWP 4825)]
[New Thread -1248445536 (LWP 4822)]
(no debugging symbols found)
0xb6f48663 in FcConfigSubstituteWithPat () from /usr/lib/libfontconfig.so.1

+ Trace 98962

Thread 6 (Thread -1256875104 (LWP 4829))

#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_realloc
from /usr/lib/libglib-2.0.so.0
#10 g_ptr_array_new
from /usr/lib/libglib-2.0.so.0
#11 g_array_append_vals
from /usr/lib/libglib-2.0.so.0
#12 g_byte_array_append
from /usr/lib/libglib-2.0.so.0
#13 camel_mime_part_construct_content_from_parser
from /usr/lib/libcamel-1.2.so.8
#14 camel_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#15 camel_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#16 camel_multipart_new
from /usr/lib/libcamel-1.2.so.8
#17 camel_multipart_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#18 camel_mime_part_construct_content_from_parser
from /usr/lib/libcamel-1.2.so.8
#19 camel_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#20 camel_mime_message_new
from /usr/lib/libcamel-1.2.so.8
#21 camel_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#22 camel_mbox_folder_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamellocal.so
#23 camel_folder_get_message
from /usr/lib/libcamel-provider-1.2.so.8
#24 mail_get_folderinfo
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#25 mail_enable_stop
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#26 e_msgport_reply
from /usr/lib/libedataserver-1.2.so.7
#27 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#28 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 palfrey 2007-01-03 18:23:13 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 352284 ***