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 581324 - crash in Evolution Mail and Calendar: Delelet email, Ctrl-E, C...
crash in Evolution Mail and Calendar: Delelet email, Ctrl-E, C...
Status: RESOLVED DUPLICATE of bug 581442
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-05-04 15:29 UTC by Dwayne Bailey
Modified: 2009-05-09 03:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Dwayne Bailey 2009-05-04 15:29:44 UTC
What were you doing when the application crashed?
Delelet email, Ctrl-E, Crash


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: 318259200 vsize: 318259200 resident: 119328768 share: 22790144 rss: 119328768 rss_rlim: 18446744073709551615
CPU usage: start_time: 1241440088 rtime: 11515 utime: 10220 stime: 1295 cutime:1 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb8074990 (LWP 20386)]
[New Thread 0xac6ffb90 (LWP 23465)]
[New Thread 0xa81feb90 (LWP 23464)]
[New Thread 0xb6970b90 (LWP 20564)]
[New Thread 0xaede1b90 (LWP 20563)]
[New Thread 0xae3e0b90 (LWP 20426)]
[New Thread 0xaf7e2b90 (LWP 20424)]
[New Thread 0xb15e5b90 (LWP 20421)]
[New Thread 0xb1fe6b90 (LWP 20420)]
[New Thread 0xb29e7b90 (LWP 20418)]
[New Thread 0xb33e8b90 (LWP 20417)]
[New Thread 0xb49fdb90 (LWP 20416)]
[New Thread 0xb53feb90 (LWP 20414)]
[New Thread 0xb5dffb90 (LWP 20413)]
[New Thread 0xb7371b90 (LWP 20411)]
[New Thread 0xb7d72b90 (LWP 20410)]
0x008ee416 in __kernel_vsyscall ()

Thread 3 (Thread 0xa81feb90 (LWP 23464))

  • #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 ---------------------
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 Fabio Durán Verdugo 2009-05-04 21:23:08 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 569700 ***
Comment 2 Akhil Laddha 2009-05-09 03:59:52 UTC

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