Bug 597330 – crash in Evolution: deleting text of a email...

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 597330 - crash in Evolution: deleting text of a email...


Summary:	crash in Evolution: deleting text of a email...


Status:	RESOLVED INCOMPLETE

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-10-04 16:55 UTC by marco.calistri
Modified:	2009-10-04 20:22 UTC

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

Description marco.calistri 2009-10-04 16:55:11 UTC

What were you doing when the application crashed?
deleting text of a email to which I were replying


Distribution: openSUSE 11.2 Milestone 8 (i586)
Gnome Release: 2.28.0 (null) (SUSE)
BugBuddy Version: 2.28.0

System: Linux 2.6.31-10-default #1 SMP 2009-09-29 11:18:23 +0200 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10604000
Selinux: No
Accessibility: Disabled
GTK+ Theme: OpenSuse-NextG-theme
Icon Theme: OxygenRefit2-green-version
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 311394304 vsize: 311394304 resident: 45314048 share: 29421568 rss: 45314048 rss_rlim: 18446744073709551615
CPU usage: start_time: 1254674922 rtime: 2482 utime: 674 stime: 1808 cutime:10 cstime: 99 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb42cfb70 (LWP 3435)]
[New Thread 0xa64d7b70 (LWP 3346)]
[New Thread 0xa7841b70 (LWP 3345)]
[New Thread 0xa8a75b70 (LWP 3328)]
[New Thread 0xb2ac0b70 (LWP 3327)]
[New Thread 0xb4ad0b70 (LWP 3321)]
[New Thread 0xb52d1b70 (LWP 3320)]
0xffffe422 in __kernel_vsyscall ()

+ Trace 218046

Thread 1 (Thread 0xb60f6760 (LWP 3315))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 <signal handler called>
#7 ??
from /usr/lib/libgtkhtml-editor.so.0
#8 gtk_html_editor_event
from /usr/lib/libgtkhtml-3.14.so.19
#9 ??
from /usr/lib/libgtkhtml-3.14.so.19
#10 html_engine_cut
from /usr/lib/libgtkhtml-3.14.so.19
#11 gtk_html_cut
from /usr/lib/libgtkhtml-3.14.so.19
#12 ??
from /usr/lib/libgtkhtml-3.14.so.19
#13 gtk_html_command
from /usr/lib/libgtkhtml-3.14.so.19
#14 ??
from /usr/lib/libgtkhtml-editor.so.0
#15 msg_composer_cut_clipboard
at e-msg-composer.c line 1786
#16 ??
from /usr/lib/libgtkhtml-editor.so.0
#17 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 ??
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_action_activate
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#25 ??
from /usr/lib/libgobject-2.0.so.0
#26 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#27 ??
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#30 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#32 ??
from /usr/lib/libgtk-x11-2.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 ??
from /usr/lib/libgobject-2.0.so.0
#36 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#37 ??
from /usr/lib/libgobject-2.0.so.0
#38 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#39 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#40 ??
from /usr/lib/libgtk-x11-2.0.so.0
#41 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#42 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#43 ??
from /usr/lib/libgdk-x11-2.0.so.0
#44 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#45 ??
from /usr/lib/libglib-2.0.so.0
#46 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#47 bonobo_main
from /usr/lib/libbonobo-2.so.0
#48 main
at main.c line 732


	Inferior 1 [process 3315] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (472 sec old) ---------------------
Try: zypper install -C "debuginfo(build-id)=653ddf906a5b35d7b66837a9b5fe1401319b72fc"
Missing separate debuginfo for /usr/lib/libicalss.so.0
Try: zypper install -C "debuginfo(build-id)=6a3ee314c98b8ea00a5f261bc3c40764003d9a55"
Missing separate debuginfo for /usr/lib/enchant/libenchant_aspell.so
Try: zypper install -C "debuginfo(build-id)=bf7a172c4c906c890a3b81c3cb4b0cf367a176e3"
Missing separate debuginfo for /usr/lib/libaspell.so.15
Try: zypper install -C "debuginfo(build-id)=14441573a1a6ea223acacfcba57c17d35235e227"
Missing separate debuginfo for /usr/lib/enchant/libenchant_ispell.so
Try: zypper install -C "debuginfo(build-id)=5d5c4f03848c995475e8801d598db8bf06d0b288"
Missing separate debuginfo for /usr/lib/enchant/libenchant_myspell.so
Try: zypper install -C "debuginfo(build-id)=2baa04a5556223d7650df7f40e4a47d4b1ec48fe"
Missing separate debuginfo for /usr/lib/libhunspell-1.2.so.0
Try: zypper install -C "debuginfo(build-id)=dc99358a2afcdda54a07e2aa45dc6e30b403c902"
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x4c00004 non valido per 0x4c03d48 (Server Aut).
Avviso del window manager: Specificato un WM_TRANSIENT_FOR finestra 0x4c00004 non valido per 0x4c04226 (Server Aut).
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-10-04 20:22:48 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 and reopen this bug or report a new one. Thanks in advance!