Bug 596594 – crash in Evolution Mail and Calendar: sending mail

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 596594 - crash in Evolution Mail and Calendar: sending mail


Summary:	crash in Evolution Mail and Calendar: sending mail


Status:	RESOLVED DUPLICATE of bug 557613

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.26.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-09-28 12:45 UTC by Paul Wise
Modified:	2009-09-29 04:15 UTC

See Also:
GNOME target:	---
GNOME version:	2.25/2.26

Description Paul Wise 2009-09-28 12:45:06 UTC

What were you doing when the application crashed?
sending mail


Distribution: Debian squeeze/sid
Gnome Release: 2.26.1 2009-04-14 (Debian)
BugBuddy Version: 2.26.0

System: Linux 2.6.30-2-amd64 #1 SMP Fri Sep 25 22:16:56 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10603901
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 848936960 vsize: 848936960 resident: 86650880 share: 27516928 rss: 86650880 rss_rlim: 18446744073709551615
CPU usage: start_time: 1254130050 rtime: 5563 utime: 3700 stime: 1863 cutime:1229 cstime: 97 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f7e50c3b950 (LWP 32259)]
[New Thread 0x7f7e4bfff950 (LWP 32233)]
[New Thread 0x7f7e559b2950 (LWP 23403)]
[New Thread 0x7f7e5412d950 (LWP 23402)]
[New Thread 0x7f7e567fc950 (LWP 23394)]
[New Thread 0x7f7e57fff950 (LWP 23334)]
[New Thread 0x7f7e61848950 (LWP 23333)]
[New Thread 0x7f7e6284a950 (LWP 23332)]
[New Thread 0x7f7e5cfee950 (LWP 23331)]
[New Thread 0x7f7e5d7ef950 (LWP 23329)]
[New Thread 0x7f7e5e637950 (LWP 23328)]
[New Thread 0x7f7e5ee38950 (LWP 23327)]
[New Thread 0x7f7e60045950 (LWP 23324)]
[New Thread 0x7f7e61047950 (LWP 23322)]
[New Thread 0x7f7e62049950 (LWP 23320)]
[New Thread 0x7f7e63273950 (LWP 23318)]
[New Thread 0x7f7e63a74950 (LWP 23316)]
0x00007f7e7268328f in __libc_waitpid (pid=32261, stat_loc=0x7fffa8e716f0, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 217909

Thread 1 (Thread 0x7f7e7d5b97f0 (LWP 23302))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 IA__g_spawn_sync
at /tmp/buildd/glib2.0-2.20.5/glib/gspawn.c line 386
#2 IA__g_spawn_command_line_sync
at /tmp/buildd/glib2.0-2.20.5/glib/gspawn.c line 700
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 __pthread_mutex_lock
at pthread_mutex_lock.c line 51
#6 e_flag_set
at e-flag.c line 83
#7 emit_async_open_response
at e-book.c line 2820
#8 g_main_dispatch
at /tmp/buildd/glib2.0-2.20.5/glib/gmain.c line 1824
#9 IA__g_main_context_dispatch
at /tmp/buildd/glib2.0-2.20.5/glib/gmain.c line 2377
#10 g_main_context_iterate
at /tmp/buildd/glib2.0-2.20.5/glib/gmain.c line 2455
#11 IA__g_main_loop_run
at /tmp/buildd/glib2.0-2.20.5/glib/gmain.c line 2663
#12 bonobo_main
from /usr/lib/libbonobo-2.so.0
#13 main
at main.c line 704

Comment 1 André Klapper 2009-09-28 13:25:15 UTC

maybe dup of bug 557613

Comment 2 Akhil Laddha 2009-09-29 04:15:53 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 557613 ***