Bug 489809 – crash in Evolution: attaching a file

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 489809 - crash in Evolution: attaching a file


Summary:	crash in Evolution: attaching a file


Status:	RESOLVED DUPLICATE of bug 460204

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.10.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-10-24 14:18 UTC by agentjayjay
Modified:	2007-10-30 04:55 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description agentjayjay 2007-10-24 14:18:21 UTC

What were you doing when the application crashed?
attaching a file


Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-13mdvlegacy #1 SMP Fri Mar 23 19:05:24 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ia Ora Blue
Icon Theme: gnome

Memory status: size: 180281344 vsize: 180281344 resident: 32468992 share: 21872640 rss: 32468992 rss_rlim: 4294967295
CPU usage: start_time: 1193235436 rtime: 420 utime: 376 stime: 44 cutime:4 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1237530912 (LWP 6685)]
[New Thread -1342272608 (LWP 6798)]
[New Thread -1297790048 (LWP 6749)]
[New Thread -1307776096 (LWP 6747)]
[New Thread -1299383392 (LWP 6746)]
[New Thread -1289163872 (LWP 6742)]
[New Thread -1261462624 (LWP 6711)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 172538

Thread 1 (Thread -1237530912 (LWP 6685))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/libpthread.so.0
#2 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 camel_header_set_param
from /usr/lib/libcamel-1.2.so.10
#5 camel_content_type_set_param
from /usr/lib/libcamel-1.2.so.10
#6 camel_mime_part_set_filename
from /usr/lib/libcamel-1.2.so.10
#7 e_attachment_new
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#8 e_attachment_bar_attach
from /usr/lib/evolution/2.10/libemiscwidgets.so.0
#9 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#10 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#11 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgtk-x11-2.0.so.0
#18 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libgtk-x11-2.0.so.0
#26 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#28 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib/libglib-2.0.so.0
#29 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#30 bonobo_main
from /usr/lib/libbonobo-2.so.0
#31 main
#0 __kernel_vsyscall



----------- .xsession-errors (12 sec old) ---------------------
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Could not write data
kio (KLauncher): ERROR: SlavePool: No communication with slave.
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KIOConnection): ERROR: Header read failed, errno=104
kio (KIOConnection): ERROR: Header has invalid size (-1)
kio (KLauncher): ERROR: SlavePool: No communication with slave.
closing
closing
closing
--------------------------------------------------

Comment 1 Akhil Laddha 2007-10-30 04:55:29 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 460204 ***