Bug 581136 – crash in Evolution Mail and Calendar: Expunging deleted mails

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 581136 - crash in Evolution Mail and Calendar: Expunging deleted mails


Summary:	crash in Evolution Mail and Calendar: Expunging deleted mails


Status:	RESOLVED DUPLICATE of bug 580575

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-05-02 20:46 UTC by Dwayne Bailey
Modified:	2009-05-04 04:34 UTC

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

Description Dwayne Bailey 2009-05-02 20:46:16 UTC

What were you doing when the application crashed?
Expunging deleted mails


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.21-170.2.56.fc10.i686 #1 SMP Mon Mar 23 23:37:54 EDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 309862400 vsize: 309862400 resident: 114184192 share: 23465984 rss: 114184192 rss_rlim: 18446744073709551615
CPU usage: start_time: 1241296700 rtime: 19419 utime: 17829 stime: 1590 cutime:104 cstime: 114 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb7f62990 (LWP 6799)]
[New Thread 0xa7affb90 (LWP 8208)]
[New Thread 0xb13fbb90 (LWP 6835)]
[New Thread 0xb1dfcb90 (LWP 6834)]
[New Thread 0xb27fdb90 (LWP 6833)]
[New Thread 0xb31feb90 (LWP 6832)]
[New Thread 0xb47dab90 (LWP 6829)]
[New Thread 0xb51dbb90 (LWP 6828)]
[New Thread 0xb5be1b90 (LWP 6827)]
[New Thread 0xb65e2b90 (LWP 6826)]
[New Thread 0xb7c60b90 (LWP 6825)]
0x00e01416 in __kernel_vsyscall ()

+ Trace 215040

Thread 2 (Thread 0xa7affb90 (LWP 8208))

#0 __kernel_vsyscall
#1 __lll_lock_wait
at ../nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S line 136
#2 _L_lock_89
from /lib/libpthread.so.0
#3 __pthread_mutex_lock
at pthread_mutex_lock.c line 86
#4 segv_redirect
at main.c line 423
#5 <signal handler called>
#6 strcmp
at ../sysdeps/i386/i686/strcmp.S line 40
#7 maildir_summary_sync
at camel-maildir-summary.c line 770
#8 camel_local_summary_sync
at camel-local-summary.c line 306
#9 local_sync
at camel-local-folder.c line 515
#10 camel_folder_sync
at camel-folder.c line 306
#11 transfer_messages_exec
at mail-ops.c line 987
#12 mail_msg_proxy
at mail-mt.c line 520
#13 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#14 g_thread_create_proxy
at gthread.c line 635
#15 start_thread
at pthread_create.c line 297
#16 clone
at ../sysdeps/unix/sysv/linux/i386/clone.S line 130



----------- .xsession-errors (7 sec old) ---------------------
warning: the debug information found in "/usr/lib/debug/usr/lib/libgssapi_krb5.so.2.2.debug" does not match "/usr/lib/libgssapi_krb5.so.2" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//lib/libuuid.so.1.2.debug" does not match "/lib/libuuid.so.1" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/lib/libuuid.so.1.2.debug" does not match "/lib/libuuid.so.1" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libkrb5support.so.0.1.debug" does not match "/usr/lib/libkrb5support.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib/libkrb5support.so.0.1.debug" does not match "/usr/lib/libkrb5support.so.0" (CRC mismatch).
--------------------------------------------------

Comment 1 Akhil Laddha 2009-05-04 04:34:14 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 580575 ***