Bug 606076 – crash in Evolution: I'd just deleted an e-ma...

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 606076 - crash in Evolution: I'd just deleted an e-ma...


Summary:	crash in Evolution: I'd just deleted an e-ma...


Status:	RESOLVED DUPLICATE of bug 606065

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	1.5.x (obsolete)
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-01-05 03:07 UTC by David Ronis
Modified:	2010-01-05 03:42 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description David Ronis 2010-01-05 03:07:02 UTC

Version: 2.30.x

What were you doing when the application crashed?
I'd just deleted an e-mail, and then had 2nd thoughts.  I switched to the trash folder and here we are.


Distribution: Slackware Slackware 12.2.0
Gnome Release: 2.29.4 2009-12-24 (GARNOME)
BugBuddy Version: 2.28.0

System: Linux 2.6.32.2 #53 SMP PREEMPT Thu Dec 24 21:07:01 EST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10799003
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad

Memory status: size: 221159424 vsize: 221159424 resident: 72089600 share: 26505216 rss: 72089600 rss_rlim: 18446744073709551615
CPU usage: start_time: 1262659430 rtime: 9243 utime: 8654 stime: 589 cutime:85 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/garnome-svn-2.29/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xb5763700 (LWP 7184)]
[New Thread 0xafaffb90 (LWP 23363)]
[New Thread 0xadaffb90 (LWP 23360)]
[New Thread 0xb02ffb90 (LWP 7209)]
[New Thread 0xb0affb90 (LWP 7208)]
[New Thread 0xb395db90 (LWP 7192)]
[New Thread 0xb415db90 (LWP 7191)]
0xb65fc171 in waitpid () from //lib/libpthread.so.0

+ Trace 219889

Thread 1 (Thread 0xb5763700 (LWP 7184))

#0 waitpid
from //lib/libpthread.so.0
#1 IA__g_spawn_sync
at gspawn.c line 386
#2 IA__g_spawn_command_line_sync
at gspawn.c line 700
#3 run_bug_buddy
at gnome-breakpad.cc line 369
#4 bugbuddy_segv_handle
at gnome-breakpad.cc line 440
#5 <signal handler called>
#6 camel_folder_summary_guess_content_info
at camel-folder-summary.c line 5089
#7 efhd_attachment_button
at em-format-html-display.c line 812
#8 efh_object_requested
at em-format-html.c line 1519
#9 html_g_cclosure_marshal_BOOLEAN__OBJECT
at htmlmarshal.c line 81
#10 IA__g_closure_invoke
at gclosure.c line 767
#11 signal_emit_unlocked_R
at gsignal.c line 3247
#12 IA__g_signal_emit_valist
at gsignal.c line 2990
#13 IA__g_signal_emit
at gsignal.c line 3037
#14 html_engine_object_requested_cb
at gtkhtml.c line 549
#15 html_g_cclosure_marshal_BOOLEAN__OBJECT
at htmlmarshal.c line 81
#16 IA__g_closure_invoke
at gclosure.c line 767
#17 signal_emit_unlocked_R
at gsignal.c line 3247
#18 IA__g_signal_emit_valist
at gsignal.c line 2990
#19 IA__g_signal_emit
at gsignal.c line 3037
#20 element_parse_object
at htmlengine.c line 1624
#21 parse_one_token
at htmlengine.c line 3975
#22 html_engine_timer_event
at htmlengine.c line 1429
#23 html_engine_flush
at htmlengine.c line 6907
#24 gtk_html_flush
at gtkhtml.c line 6317
#25 emhs_sync_flush
at em-html-stream.c line 86
#26 emss_process_message
at em-sync-stream.c line 87
#27 g_idle_dispatch
at gmain.c line 4065
#28 IA__g_main_context_dispatch
at gmain.c line 1960
#29 g_main_context_iterate
at gmain.c line 2591
#30 IA__g_main_loop_run
at gmain.c line 2799
#31 IA__gtk_main
at gtkmain.c line 1219
#32 main
at main.c line 593
#0 waitpid
from //lib/libpthread.so.0

Comment 1 Akhil Laddha 2010-01-05 03:42:22 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 bug 606065 ***