Bug 397153 – crash in Evolution:

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 397153 - crash in Evolution:


Summary:	crash in Evolution:


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-16 07:23 UTC by finnam
Modified:	2007-01-18 17:55 UTC

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

Description finnam 2007-01-16 07:23:22 UTC

What were you doing when the application crashed?



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

Memory status: size: -1125191680 vsize: 0 resident: -1125191680 share: 0 rss: 377860096 rss_rlim: 0
CPU usage: start_time: 1168871163 rtime: 0 utime: 2616 stime: 0 cutime:1620 cstime: 0 timeout: 996 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 -1232783696 (LWP 20019)]
[New Thread -1297093728 (LWP 20035)]
[New Thread -1288701024 (LWP 20034)]
[New Thread -1278829664 (LWP 20033)]
[New Thread -1258677344 (LWP 20029)]
[New Thread -1250284640 (LWP 20027)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 102612

Thread 5 (Thread -1258677344 (LWP 20029))

#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_message_new
from /usr/lib/libcamel-1.2.so.8
#16 camel_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#17 camel_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#18 camel_data_wrapper_construct_from_stream
from /usr/lib/libcamel-1.2.so.8
#19 camel_pop3_engine_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
#20 camel_pop3_delete_old
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
#21 camel_pop3_folder_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
#22 camel_folder_sync
from /usr/lib/libcamel-provider-1.2.so.8
#23 mail_fetch_mail
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#24 mail_enable_stop
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#25 e_msgport_reply
from /usr/lib/libedataserver-1.2.so.7
#26 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#27 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 Kjartan Maraas 2007-01-16 15:21:30 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Akhil Laddha 2007-01-17 04:54:26 UTC

May be duplicate of Bug 376826

Comment 3 palfrey 2007-01-18 17:55:54 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 ***