Bug 576319 – crash in Evolution Mail and Calendar: starting evolution

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 576319 - crash in Evolution Mail and Calendar: starting evolution


Summary:	crash in Evolution Mail and Calendar: starting evolution


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:49 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:49:07 UTC

What were you doing when the application crashed?
starting evolution


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: 112226304 vsize: 112226304 resident: 31158272 share: 19701760 rss: 31158272 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237751117 rtime: 309 utime: 272 stime: 37 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 0xb6259980 (LWP 4285)]
[New Thread 0xb2ee1b90 (LWP 4374)]
[New Thread 0xb45ffb90 (LWP 4314)]
[New Thread 0xb57ecb90 (LWP 4311)]
0xb7f65424 in __kernel_vsyscall ()

+ Trace 213733

Thread 1 (Thread 0xb6259980 (LWP 4285))

#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 ??
from /usr/lib/libdbus-glib-1.so.2
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#0 __kernel_vsyscall

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