Bug 388737 – crash in Evolution: saving 50 attachments

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 388737 - crash in Evolution: saving 50 attachments


Summary:	crash in Evolution: saving 50 attachments


Status:	RESOLVED DUPLICATE of bug 340165

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:	2006-12-22 20:26 UTC by wvd
Modified:	2007-02-09 07:41 UTC

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

Description wvd 2006-12-22 20:26:47 UTC

What were you doing when the application crashed?
saving 50 attachments


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.2 2006-11-20 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 199450624 vsize: 0 resident: 199450624 share: 0 rss: 63422464 rss_rlim: 0
CPU usage: start_time: 1166817737 rtime: 0 utime: 5389 stime: 0 cutime:5139 cstime: 0 timeout: 250 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1234532688 (LWP 9771)]
[New Thread -1328231536 (LWP 9820)]
[New Thread -1305760880 (LWP 9814)]
[New Thread -1297036400 (LWP 9813)]
[New Thread -1272153200 (LWP 9787)]
[New Thread -1263367280 (LWP 9785)]
[New Thread -1254941808 (LWP 9783)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 96323

Thread 1 (Thread -1234532688 (LWP 9771))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/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_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 em_format_html_display_new
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#11 em_format_html_new
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#12 html_g_cclosure_marshal_BOOLEAN__OBJECT
from /usr/lib/libgtkhtml-3.8.so.15
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 gtk_html_get_top_html
from /usr/lib/libgtkhtml-3.8.so.15
#18 html_g_cclosure_marshal_BOOLEAN__OBJECT
from /usr/lib/libgtkhtml-3.8.so.15
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
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 html_engine_flush
from /usr/lib/libgtkhtml-3.8.so.15
#24 html_engine_replace_do
from /usr/lib/libgtkhtml-3.8.so.15
#25 html_engine_begin
from /usr/lib/libgtkhtml-3.8.so.15
#26 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_dispatch
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

Comment 1 Kjartan Maraas 2007-01-16 12:09: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 Kjartan Maraas 2007-02-09 07:41:24 UTC

Likely a duplicate of bug 340165 or 333864. Fixed in 2.8.3 and 2.9.x

*** This bug has been marked as a duplicate of 340165 ***