Bug 598591 – crash in Evolution Mail and Calendar: Deleting an email from m...

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 598591 - crash in Evolution Mail and Calendar: Deleting an email from m...


Summary:	crash in Evolution Mail and Calendar: Deleting an email from m...


Status:	RESOLVED DUPLICATE of bug 561332

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-10-15 16:59 UTC by scott.parkerson
Modified:	2009-10-15 23:15 UTC

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

Description scott.parkerson 2009-10-15 16:59:47 UTC

What were you doing when the application crashed?
Deleting an email from my Gmail account; I suppose this happened in the Exchange connector on the other account.


Distribution: Unknown
Gnome Release: 2.26.3 2009-07-02 (Foresight Linux)
BugBuddy Version: 2.26.0

System: Linux 2.6.30.6-2-fl.smp.gcc4.1.x86_64 #1 SMP Mon Sep 14 22:19:36 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10603000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 428093440 vsize: 428093440 resident: 20242432 share: 12042240 rss: 20242432 rss_rlim: 18446744073709551615
CPU usage: start_time: 1255625231 rtime: 51 utime: 37 stime: 14 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution/2.26/evolution-exchange-storage'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0x7f6a504bb750 (LWP 2900)]
[New Thread 0x414ef940 (LWP 2907)]
0x00007f6a4a2949ff in waitpid () from /lib64/libpthread.so.0

+ Trace 218341

Thread 1 (Thread 0x7f6a504bb750 (LWP 2900))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_spawn_sync
from /usr/lib64/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib64/libglib-2.0.so.0
#3 ??
from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 g_str_hash
from /usr/lib64/libglib-2.0.so.0
#6 ??
from /usr/lib64/libglib-2.0.so.0
#7 g_hash_table_lookup
from /usr/lib64/libglib-2.0.so.0
#8 message_removed
at mail-stub-exchange.c line 405
#9 sync_deletions
at mail-stub-exchange.c line 1219
#10 connection_handler
at mail-stub.c line 168
#11 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#12 ??
from /usr/lib64/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#14 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#15 main
at main.c line 278
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (47 sec old) ---------------------
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
camel-Message: --
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
** (evolution:3128): DEBUG: EI: mail_read_notify
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-10-15 23:15:27 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 561332 ***