Bug 378587 – crash in Evolution: esta aplicacion se cuelg...

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 378587 - crash in Evolution: esta aplicacion se cuelg...


Summary:	crash in Evolution: esta aplicacion se cuelg...


Status:	RESOLVED DUPLICATE of bug 376826

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:

Duplicates:	427853 427878 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-23 19:12 UTC by arielfg
Modified:	2007-04-09 21:02 UTC

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

Description arielfg 2006-11-23 19:12:35 UTC

What were you doing when the application crashed?
esta aplicacion se cuelga desde la instalacion previa. pudiera influir que este es un pc con 2 athlon-mp, ¿?, el evolution estaba recolectando correo de tipo http. con cifrado.


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

Memory status: size: 662253568 vsize: 0 resident: 662253568 share: 0 rss: 256020480 rss_rlim: 0
CPU usage: start_time: 1164308326 rtime: 0 utime: 1495 stime: 0 cutime:812 cstime: 0 timeout: 683 it_real_value: 0 frequency: 3844

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 -1232472400 (LWP 21382)]
[New Thread -1314686048 (LWP 21425)]
[New Thread -1294382176 (LWP 21401)]
[New Thread -1296041056 (LWP 21400)]
[New Thread -1285596256 (LWP 21398)]
[New Thread -1277203552 (LWP 21397)]
[New Thread -1257256032 (LWP 21391)]
[New Thread -1265685600 (LWP 21390)]
[New Thread -1248863328 (LWP 21387)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 88853

Thread 6 (Thread -1277203552 (LWP 21397))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libc.so.6
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 874
#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
at gmessages.c line 497
#8 IA__g_log
at gmessages.c line 517
#9 IA__g_realloc
at gmem.c line 172
#10 g_array_maybe_expand
at garray.c line 339
#11 IA__g_array_append_vals
at garray.c line 132
#12 IA__g_byte_array_append
at garray.c line 653
#13 camel_mime_part_construct_content_from_parser
at camel-mime-part-utils.c line 71
#14 construct_from_parser
at camel-mime-part.c line 961
#15 camel_mime_part_construct_from_parser
at camel-mime-part.c line 989
#16 construct_from_parser
at camel-multipart.c line 566
#17 camel_multipart_construct_from_parser
at camel-multipart.c line 598
#18 camel_mime_part_construct_content_from_parser
at camel-mime-part-utils.c line 119
#19 construct_from_parser
at camel-mime-part.c line 961
#20 construct_from_parser
at camel-mime-message.c line 590
#21 camel_mime_part_construct_from_parser
at camel-mime-part.c line 989
#22 mbox_get_message
at camel-mbox-folder.c line 406
#23 camel_folder_get_message
at camel-folder.c line 1070
#24 send_queue_send
at mail-ops.c line 466
#25 mail_msg_received
at mail-mt.c line 570
#26 thread_dispatch
at e-msgport.c line 987
#27 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#28 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 André Klapper 2006-11-27 17:04:36 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 376826 ***

Comment 2 palfrey 2007-04-09 14:28:08 UTC

*** Bug 427853 has been marked as a duplicate of this bug. ***

Comment 3 palfrey 2007-04-09 21:02:03 UTC

*** Bug 427878 has been marked as a duplicate of this bug. ***