Bug 576321 – crash in Evolution Mail and Calendar: starting evo (this time ...

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 576321 - crash in Evolution Mail and Calendar: starting evo (this time ...


Summary:	crash in Evolution Mail and Calendar: starting evo (this time ...


Status:	RESOLVED DUPLICATE of bug 575587

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:

Depends on:
Blocks:

Reported:	2009-03-22 19:54 UTC by bugreports
Modified:	2009-03-23 03:40 UTC

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

Description bugreports 2009-03-22 19:54:44 UTC

What were you doing when the application crashed?
starting evo (this time with debug packages for sqlite and dbus-glib)


Distribution: Debian squeeze/sid
Gnome Release: 2.24.2 2009-01-04 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.29-rc7-git-sonne #4 SMP PREEMPT Fri Mar 6 11:35:41 CET 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10599901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 109617152 vsize: 109617152 resident: 30064640 share: 19611648 rss: 30064640 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237751520 rtime: 150 utime: 137 stime: 13 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 0xb6211980 (LWP 7262)]
[New Thread 0xb2693b90 (LWP 7282)]
[New Thread 0xb57a4b90 (LWP 7279)]
[New Thread 0xb37fcb90 (LWP 7273)]
[New Thread 0xb45ffb90 (LWP 7272)]
0xb7f1d424 in __kernel_vsyscall ()

+ Trace 213734

Thread 1 (Thread 0xb6211980 (LWP 7262))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gspawn.c line 382
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gspawn.c line 694
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 segv_redirect
at main.c line 414
#7 <signal handler called>
#8 camel_message_info_uint32
at camel-folder-summary.c line 4547
#9 ??
from /usr/lib/evolution/2.24/plugins/liborg-jylefort-mail-notification.so
#10 ??
#11 ??
#12 ??
#13 ??
#14 ??
from /usr/lib/libdbus-glib-1.so.2
#15 ??
#16 ??
#17 IA__g_type_value_table_peek
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/gobject/gtype.c line 3893
#18 dbus_glib_marshal_mn_evolution_server_BOOLEAN__STRING_POINTER_POINTER
from /usr/lib/evolution/2.24/plugins/liborg-jylefort-mail-notification.so
#19 gobject_message_function
at dbus-gobject.c line 1347
#20 ??
from /usr/lib/libdbus-1.so.3
#21 ??
#22 ??
#23 ??
#24 ??
from /usr/lib/libdbus-1.so.3
#25 ??
#26 ??
from /usr/lib/libdbus-1.so.3
#27 ??
#28 ??
#29 __pthread_mutex_lock
at pthread_mutex_lock.c line 43
#30 dbus_connection_dispatch
from /usr/lib/libdbus-1.so.3
#31 message_queue_dispatch
at dbus-gmain.c line 101
#32 IA__g_main_context_dispatch
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gmain.c line 1814
#33 g_main_context_iterate
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gmain.c line 2448
#34 IA__g_main_loop_run
at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gmain.c line 2656
#35 bonobo_main
from /usr/lib/libbonobo-2.so.0
#36 main
at main.c line 690
#0 __kernel_vsyscall

Comment 1 Akhil Laddha 2009-03-23 03:40:24 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 575587 ***