Bug 597206 – crash in Evolution Mail and Calendar: Trying to reply to an em...

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 597206 - crash in Evolution Mail and Calendar: Trying to reply to an em...


Summary:	crash in Evolution Mail and Calendar: Trying to reply to an em...


Status:	RESOLVED DUPLICATE of bug 596282

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.28.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:	2009-10-03 13:30 UTC by flameeyes
Modified:	2009-10-04 00:38 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description flameeyes 2009-10-03 13:30:07 UTC

What were you doing when the application crashed?
Trying to reply to an email…


Distribution: Gentoo Base System release 2.0.1
Gnome Release: 2.28.0 2009-09-30 (Gentoo)
BugBuddy Version: 2.26.0

System: Linux 2.6.31 #9 SMP PREEMPT Mon Sep 28 02:35:32 CEST 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10604000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka-Gilouche
Icon Theme: Mist
GTK+ Modules: gnomebreakpad

Memory status: size: 717860864 vsize: 717860864 resident: 46198784 share: 24178688 rss: 46198784 rss_rlim: 18446744073709551615
CPU usage: start_time: 1254576492 rtime: 147 utime: 136 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f0fe50b7730 (LWP 27451)]
[New Thread 0x7f0fbedba910 (LWP 27810)]
[New Thread 0x7f0fbf5bb910 (LWP 27809)]
[New Thread 0x7f0fcca2a910 (LWP 27783)]
[New Thread 0x7f0fc7fff910 (LWP 27512)]
[New Thread 0x7f0fc77fe910 (LWP 27494)]
[New Thread 0x7f0fcd22b910 (LWP 27491)]
[New Thread 0x7f0fce578910 (LWP 27484)]
[New Thread 0x7f0fced79910 (LWP 27482)]
[New Thread 0x7f0fd01b1910 (LWP 27480)]
[New Thread 0x7f0fd09b2910 (LWP 27479)]
0x00007f0fe25c259d in __libc_waitpid (pid=27813, 
    stat_loc=<value optimized out>, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 218022

Thread 1 (Thread 0x7f0fe50b7730 (LWP 27451))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 IA__g_spawn_sync
at gspawn.c line 386
#2 IA__g_spawn_command_line_sync
at gspawn.c line 700
#3 bugbuddy_segv_handle
at gnome-breakpad.cc line 369
#4 <signal handler called>
#5 editor_method_event
at gtkhtml-editor.c line 387
#6 gtk_html_editor_event
at gtkhtml.c line 5991
#7 delete_object
at htmlengine-edit-cut-and-paste.c line 798
#8 html_engine_delete
at htmlengine-edit-cut-and-paste.c line 1914
#9 command
at gtkhtml.c line 5225
#10 gtk_html_command
at gtkhtml.c line 6009
#11 e_msg_composer_show_sig_file
at e-msg-composer.c line 3796
#12 msg_composer_init
at e-msg-composer.c line 2245
#13 IA__g_type_create_instance
at gtype.c line 1674
#14 g_object_constructor
at gobject.c line 1338
#15 editor_constructor
at gtkhtml-editor.c line 509
#16 msg_composer_constructor
at e-msg-composer.c line 1530
#17 IA__g_object_newv
at gobject.c line 1215
#18 IA__g_object_new_valist
at gobject.c line 1278
#19 IA__g_object_new
at gobject.c line 1060
#20 em_utils_reply_to_message
at em-composer-utils.c line 1747
#21 reply_to_message
at em-composer-utils.c line 2306
#22 mail_msg_idle_cb
at mail-mt.c line 502
#23 IA__g_main_context_dispatch
at gmain.c line 1960
#24 g_main_context_iterate
at gmain.c line 2591
#25 IA__g_main_loop_run
at gmain.c line 2799
#26 bonobo_main
at bonobo-main.c line 311
#27 main
at main.c line 732



----------- .xsession-errors (161522 sec old) ---------------------
Avviso del window manager: Lo schermo 0 sul display «:0.0» ha già un window manager; provare a utilizzare l'opzione --replace per sostituirlo.
Avviso del window manager: Lettura del file della sessione /home/flame/.config/metacity/sessions/10c3091dbcc0d20a61125441494088030100000206950027.ms non riuscita: Apertura del file "/home/flame/.confi
Avviso del window manager: Lo schermo 0 sul display «:0.0» ha già un window manager; provare a utilizzare l'opzione --replace per sostituirlo.
Avviso del window manager: Lettura del file della sessione /home/flame/.config/metacity/sessions/10c3091dbcc0d20a61125441494088030100000206950027.ms non riuscita: Apertura del file "/home/flame/.confi
Avviso del window manager: Lo schermo 0 sul display «:0.0» ha già un window manager; provare a utilizzare l'opzione --replace per sostituirlo.
Avviso del window manager: Lettura del file della sessione /home/flame/.config/metacity/sessions/10c3091dbcc0d20a61125441494088030100000206950027.ms non riuscita: Apertura del file "/home/flame/.confi
Avviso del window manager: Lo schermo 0 sul display «:0.0» ha già un window manager; provare a utilizzare l'opzione --replace per sostituirlo.
Avviso del window manager: Lettura del file della sessione /home/flame/.config/metacity/sessions/10c3091dbcc0d20a61125441494088030100000206950027.ms non riuscita: Apertura del file "/home/flame/.confi
Avviso del window manager: Lo schermo 0 sul display «:0.0» ha già un window manager; provare a utilizzare l'opzione --replace per sostituirlo.
Avviso del window manager: Lettura del file della sessione /home/flame/.config/metacity/sessions/10c3091dbcc0d20a61125441494088030100000206950027.ms non riuscita: Apertura del file "/home/flame/.confi
Avviso del window manager: Lo schermo 0 sul display «:0.0» ha già un window manager; provare a utilizzare l'opzione --replace per sostituirlo.
Avviso del window manager: Lettura del file della sessione /home/flame/.config/metacity/sessions/10c3091dbcc0d20a61125441494088030100000206950027.ms non riuscita: Apertura del file "/home/flame/.confi
Avviso del window manager: Lo schermo 0 sul display «:0.0» ha già un window manager; provare a utilizzare l'opzione --replace per sostituirlo.
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-10-04 00:38: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 596282 ***