Bug 391736 – crash in Evolution: copying picture files

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 391736 - crash in Evolution: copying picture files


Summary:	crash in Evolution: copying picture files


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-02 02:53 UTC by nodor
Modified:	2007-01-02 18:50 UTC

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

Description nodor 2007-01-02 02:53:00 UTC

What were you doing when the application crashed?
copying picture files


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

Memory status: size: -1131909120 vsize: 0 resident: -1131909120 share: 0 rss: 694693888 rss_rlim: 0
CPU usage: start_time: 1167672121 rtime: 0 utime: 3770 stime: 0 cutime:2032 cstime: 0 timeout: 1738 it_real_value: 0 frequency: 4597

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 -1233426768 (LWP 5035)]
[New Thread -1347421280 (LWP 5089)]
[New Thread -1346016352 (LWP 5060)]
[New Thread -1337312352 (LWP 5050)]
[New Thread -1328919648 (LWP 5049)]
[New Thread -1320125536 (LWP 5048)]
[New Thread -1279231072 (LWP 5042)]
[New Thread -1270801504 (LWP 5039)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 98599

Thread 8 (Thread -1270801504 (LWP 5039))

#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_mime_part_construct_from_parser
from /usr/lib/libcamel-1.2.so.8
#23 camel_data_wrapper_construct_from_stream
from /usr/lib/libcamel-1.2.so.8
#24 camel_pop3_engine_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
#25 camel_pop3_delete_old
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
#26 camel_pop3_folder_new
from /usr/lib/evolution-data-server-1.2/camel-providers-8/libcamelpop3.so
#27 camel_folder_sync
from /usr/lib/libcamel-provider-1.2.so.8
#28 fetch_mail_fetch
at mail-ops.c line 345
#29 mail_msg_received
at mail-mt.c line 570
#30 e_msgport_reply
from /usr/lib/libedataserver-1.2.so.7
#31 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#32 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 palfrey 2007-01-02 18:50: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 ***