Bug 588701 – crash in Evolution Mail and Calendar: Closting Evo

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 588701 - crash in Evolution Mail and Calendar: Closting Evo


Summary:	crash in Evolution Mail and Calendar: Closting Evo


Status:	RESOLVED DUPLICATE of bug 570329

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.26.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-07-15 19:15 UTC by Dwayne Bailey
Modified:	2009-07-16 03:41 UTC

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

Description Dwayne Bailey 2009-07-15 19:15:59 UTC

What were you doing when the application crashed?
Closting Evo


Distribution: Fedora release 11 (Leonidas)
Gnome Release: 2.26.2 2009-06-01 (Red Hat, Inc)
BugBuddy Version: 2.26.0

System: Linux 2.6.29.5-191.fc11.i686.PAE #1 SMP Tue Jun 16 23:19:53 EDT 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10601901
Selinux: Permissive
Accessibility: Enabled
GTK+ Theme: Nodoka
Icon Theme: Fedora
GTK+ Modules: canberra-gtk-module, pk-gtk-module, gail:atk-bridge, gnomebreakpad

Memory status: size: 315543552 vsize: 315543552 resident: 137056256 share: 23605248 rss: 137056256 rss_rlim: 18446744073709551615
CPU usage: start_time: 1247684011 rtime: 10566 utime: 9517 stime: 1049 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 0xa82ffb70 (LWP 10268)]
[New Thread 0xb64ffb70 (LWP 10259)]
[New Thread 0xb725db70 (LWP 9966)]
[New Thread 0xae9ffb70 (LWP 9964)]
[New Thread 0xb1a31b70 (LWP 9952)]
[New Thread 0xb2432b70 (LWP 9951)]
[New Thread 0xb2e33b70 (LWP 9950)]
[New Thread 0xb44fdb70 (LWP 9949)]
[New Thread 0xb4efeb70 (LWP 9947)]
[New Thread 0xb58ffb70 (LWP 9946)]
[New Thread 0xb70ffb70 (LWP 9943)]
[New Thread 0xb7cbab70 (LWP 9942)]
0x0081b424 in __kernel_vsyscall ()

+ Trace 216473

Thread 3 (Thread 0xb64ffb70 (LWP 10259))

#0 __kernel_vsyscall
#1 __lll_lock_wait
at ../nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S line 142
#2 _L_lock_752
from /lib/libpthread.so.0
#3 __pthread_mutex_lock
at pthread_mutex_lock.c line 61
#4 segv_redirect
at main.c line 435
#5 <signal handler called>
#6 strcmp
at ../sysdeps/i386/i686/strcmp.S line 40
#7 maildir_summary_sync
at camel-maildir-summary.c line 771
#8 camel_local_summary_sync
at camel-local-summary.c line 306
#9 local_sync
at camel-local-folder.c line 517
#10 camel_folder_sync
at camel-folder.c line 324
#11 transfer_messages_exec
at mail-ops.c line 993
#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



---- Critical and fatal warnings logged during execution ----

** Gdk **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed 


----------- .xsession-errors ---------------------
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libgsf-1.so.114" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libbeagle.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: "/usr/lib/debug/usr/lib/gconv/libJIS.so.debug": The separate debug info file has no debug info
warning: "/usr/lib/debug/usr/lib/gconv/libGB.so.debug": The separate debug info file has no debug info
warning: "/usr/lib/debug/usr/lib/gconv/libKSC.so.debug": The separate debug info file has no debug info
--------------------------------------------------

Comment 1 Akhil Laddha 2009-07-16 03:41:00 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 570329 ***