Bug 580876 – crash in Evolution Mail and Calendar: Not sure what I was doin...

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 580876 - crash in Evolution Mail and Calendar: Not sure what I was doin...


Summary:	crash in Evolution Mail and Calendar: Not sure what I was doin...


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-04-30 13:02 UTC by Dwayne Bailey
Modified:	2009-04-30 15:39 UTC

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

Description Dwayne Bailey 2009-04-30 13:02:55 UTC

What were you doing when the application crashed?
Not sure what I was doing....


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: 327921664 vsize: 327921664 resident: 133414912 share: 25190400 rss: 133414912 rss_rlim: 18446744073709551615
CPU usage: start_time: 1241082853 rtime: 66850 utime: 63737 stime: 3113 cutime:103 cstime: 116 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb805e990 (LWP 17235)]
[New Thread 0xaa3fdb90 (LWP 31568)]
[New Thread 0xaadfeb90 (LWP 31535)]
[New Thread 0xa99fcb90 (LWP 18472)]
[New Thread 0xb34ffb90 (LWP 18471)]
[New Thread 0xb13fbb90 (LWP 17271)]
[New Thread 0xb1dfcb90 (LWP 17270)]
[New Thread 0xb27fdb90 (LWP 17269)]
[New Thread 0xb31feb90 (LWP 17268)]
[New Thread 0xb47e3b90 (LWP 17265)]
[New Thread 0xb51e4b90 (LWP 17264)]
[New Thread 0xb5beab90 (LWP 17263)]
[New Thread 0xb65ebb90 (LWP 17262)]
[New Thread 0xb7d5cb90 (LWP 17261)]
0x006ac416 in __kernel_vsyscall ()

+ Trace 214965

Thread 3 (Thread 0xaadfeb90 (LWP 31535))

#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 (8 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 palfrey 2009-04-30 15:39:58 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 ***