Bug 570654 – crash in Evolution Mail and Calendar:

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 570654 - crash in Evolution Mail and Calendar:


Summary:	crash in Evolution Mail and Calendar:


Status:	RESOLVED DUPLICATE of bug 569892

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

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

URL:
Whiteboard:

Duplicates:	570655 572550 (view as bug list)
Depends on:
Blocks:

Reported:	2009-02-05 15:21 UTC by jaroslav.pulchart
Modified:	2009-02-26 09:34 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description jaroslav.pulchart 2009-02-05 15:21:39 UTC

What were you doing when the application crashed?



Distribution: CentOS release 5 (Final)
Gnome Release: 2.24.3 2009-01-13 (GARNOME)
BugBuddy Version: 2.24.0

System: Linux 2.6.18-8.1.15.el5 #1 SMP Mon Oct 22 08:32:04 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nodoka
Icon Theme: Foxtrot

Memory status: size: 101515264 vsize: 101515264 resident: 37486592 share: 21909504 rss: 37486592 rss_rlim: 18446744073709551615
CPU usage: start_time: 1233847083 rtime: 396 utime: 359 stime: 37 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/home/pulcharj/opt/usr/bin/evolution'

(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 -1232427312 (LWP 1353)]
0xb7f21402 in __kernel_vsyscall ()

+ Trace 212253

Thread 1 (Thread -1232427312 (LWP 1353))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 g_spawn_sync
from /home/pulcharj/opt/usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /home/pulcharj/opt/usr/lib/libglib-2.0.so.0
#4 run_bug_buddy
from /home/pulcharj/opt/usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 bugbuddy_segv_handle
from /home/pulcharj/opt/usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 <signal handler called>
#7 g_object_ref
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#8 gtk_grab_notify_foreach
from /home/pulcharj/opt/usr/lib/libgtk-x11-2.0.so.0
#9 gtk_bin_forall
from /home/pulcharj/opt/usr/lib/libgtk-x11-2.0.so.0
#10 gtk_container_forall
from /home/pulcharj/opt/usr/lib/libgtk-x11-2.0.so.0
#11 gtk_grab_notify_foreach
from /home/pulcharj/opt/usr/lib/libgtk-x11-2.0.so.0
#12 gtk_grab_notify
from /home/pulcharj/opt/usr/lib/libgtk-x11-2.0.so.0
#13 gtk_window_show
from /home/pulcharj/opt/usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__VOID
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#15 g_type_class_meta_marshal
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#16 g_closure_invoke
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#17 signal_emit_unlocked_R
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#19 g_signal_emit
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#20 gtk_widget_show
from /home/pulcharj/opt/usr/lib/libgtk-x11-2.0.so.0
#21 gtk_dialog_run
from /home/pulcharj/opt/usr/lib/libgtk-x11-2.0.so.0
#22 _gtk_print_operation_platform_backend_run_dialog
from /home/pulcharj/opt/usr/lib/libgtk-x11-2.0.so.0
#23 gtk_print_operation_run
from /home/pulcharj/opt/usr/lib/libgtk-x11-2.0.so.0
#24 html_engine_print_operation_run
from /home/pulcharj/opt/usr/lib/libgtkhtml-3.14.so.19
#25 gtk_html_print_operation_run
from /home/pulcharj/opt/usr/lib/libgtkhtml-3.14.so.19
#26 emfhp_complete
from /home/pulcharj/opt/usr/lib/evolution/2.24/components/libevolution-mail.so
#27 g_cclosure_marshal_VOID__VOID
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#28 g_closure_invoke
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#29 signal_emit_unlocked_R
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#30 g_signal_emit_valist
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#31 g_signal_emit_by_name
from /home/pulcharj/opt/usr/lib/libgobject-2.0.so.0
#32 efh_format_done
from /home/pulcharj/opt/usr/lib/evolution/2.24/components/libevolution-mail.so
#33 mail_msg_idle_cb
from /home/pulcharj/opt/usr/lib/evolution/2.24/components/libevolution-mail.so
#34 g_idle_dispatch
from /home/pulcharj/opt/usr/lib/libglib-2.0.so.0
#35 g_main_context_dispatch
from /home/pulcharj/opt/usr/lib/libglib-2.0.so.0
#36 g_main_context_iterate
from /home/pulcharj/opt/usr/lib/libglib-2.0.so.0
#37 g_main_loop_run
from /home/pulcharj/opt/usr/lib/libglib-2.0.so.0
#38 bonobo_main
from /home/pulcharj/opt/usr/lib/libbonobo-2.so.0
#39 main
#0 __kernel_vsyscall

Comment 1 André Klapper 2009-02-05 23:59:15 UTC

*** Bug 570655 has been marked as a duplicate of this bug. ***

Comment 2 Akhil Laddha 2009-02-06 04:02:17 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.
Could you please install some debugging packages [1], start the application as
normal, and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the Details, now
containing way more information. Please copy that stacktrace and paste it as a
comment here. Thanks in advance!

[1] debugging packages for evolution, evolution-data-server, evolution-exchange, gtkhtml, gtk, glib, libsoup, gnome-vfs, libgnome, orbit2 and libgnomeui (as far as those packages are provided by your distribution). More details can be found here:
http://live.gnome.org/GettingTraces

Comment 3 Milan Crha 2009-02-26 09:22:53 UTC

*** Bug 572550 has been marked as a duplicate of this bug. ***

Comment 4 Milan Crha 2009-02-26 09:34:50 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 569892 ***