Bug 598245 – crash in Evolution Mail and Calendar: Sending an 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 598245 - crash in Evolution Mail and Calendar: Sending an email


Summary:	crash in Evolution Mail and Calendar: Sending an email


Status:	RESOLVED DUPLICATE of bug 535516

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.24.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-10-13 09:15 UTC by vms
Modified:	2009-10-13 10:54 UTC

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

Description vms 2009-10-13 09:15:53 UTC

What were you doing when the application crashed?
Sending an email


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.24.3 2009-06-13 (Gentoo)
BugBuddy Version: 2.24.2

System: Linux 2.6.27-gentoo-r8 #1 SMP PREEMPT Tue Mar 10 23:38:03 CET 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 194781184 vsize: 194781184 resident: 61337600 share: 26890240 rss: 61337600 rss_rlim: 18446744073709551615
CPU usage: start_time: 1255425096 rtime: 1201 utime: 1100 stime: 101 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 0xb55ee720 (LWP 5601)]
[New Thread 0xad527b90 (LWP 6029)]
[New Thread 0xadd28b90 (LWP 6027)]
[New Thread 0xb2a10b90 (LWP 5651)]
[New Thread 0xb0aafb90 (LWP 5649)]
0xb80b3424 in __kernel_vsyscall ()

+ Trace 218262

Thread 1 (Thread 0xb55ee720 (LWP 5601))

#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 run_bug_buddy
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 check_if_gdb
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 bugbuddy_segv_handle
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#7 <signal handler called>
#8 g_type_check_instance_cast
from /usr/lib/libgobject-2.0.so.0
#9 window_binding_perform_scheduled_sync
from /usr/lib/evolution/2.24/libeutil.so.0
#10 g_timeout_dispatch
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_iterate
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 bonobo_main
from /usr/lib/libbonobo-2.so.0
#15 main
#0 __kernel_vsyscall



----------- .xsession-errors (160 sec old) ---------------------
(evolution:5601): camel-imap-provider-WARNING **: Unable to load summary no such table: [Gmail]/Mesaje importante
(evolution:5601): camel-imap-provider-WARNING **: Unable to load summary no such table: INBOX/lists/svn
(evolution:5601): camel-imap-provider-WARNING **: Unable to load summary no such table: INBOX/lists/forums
(evolution:5601): camel-imap-provider-WARNING **: Unable to load summary no such table: INBOX/lists/aikido
(11:12:45) jabber: Sending (ssl): <iq type='get' id='purple65a76441'><ping xmlns='urn:xmpp:ping'/></iq>
(11:12:45) jabber: Recv (ssl)(244): <iq from='vladmihaisima@jabber.org' to='vladmihaisima@jabber.org/Gaim' type='error' id='purple65a76441'><ping xmlns='urn:xmpp:ping'/><error code='503' type='cancel'
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Akhil Laddha 2009-10-13 10:54:55 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 535516 ***