Bug 608628 – crash in Evolution: I'd just started evoluti...

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 608628 - crash in Evolution: I'd just started evoluti...


Summary:	crash in Evolution: I'd just started evoluti...


Status:	RESOLVED INCOMPLETE

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.28.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:	2010-01-31 20:38 UTC by David Ronis
Modified:	2010-03-03 06:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.27/2.28

Description David Ronis 2010-01-31 20:38:25 UTC

Version: 2.30.x

What were you doing when the application crashed?
I'd just started evolution after a crash.  This is on my wife's machine which is running gnome 2.28.0 other than evolution and friends which are all git master versions.


Distribution: Slackware Slackware 13.0.0.0.0
Gnome Release: 2.28.0 2009-10-30 (GARNOME)
BugBuddy Version: 2.28.0

System: Linux 2.6.32.2 #23 SMP PREEMPT Fri Dec 25 10:27:46 EST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10799002
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad

Memory status: size: 162918400 vsize: 162918400 resident: 39960576 share: 23875584 rss: 39960576 rss_rlim: 18446744073709551615
CPU usage: start_time: 1264970185 rtime: 1119 utime: 929 stime: 190 cutime:42 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/garnome-svn-2.28/bin/evolution'

[Thread debugging using libthread_db enabled]
[New Thread 0xb58b2a10 (LWP 313)]
[New Thread 0xaf2ffb90 (LWP 340)]
[New Thread 0xb0affb90 (LWP 335)]
[New Thread 0xb436ab90 (LWP 334)]
[New Thread 0xb4c71b90 (LWP 326)]
[New Thread 0xb5471b90 (LWP 325)]
0xb5b7b9b1 in waitpid () from //lib/libpthread.so.0

+ Trace 220343

Thread 2 (Thread 0xaf2ffb90 (LWP 340))

#0 __lll_lock_wait
from //lib/libpthread.so.0
#1 _L_lock_89
from //lib/libpthread.so.0
#2 pthread_mutex_lock
from //lib/libpthread.so.0
#3 <signal handler called>
#4 camel_operation_unref
from /opt/garnome-svn-2.28/lib/libcamel-1.2.so.14
#5 ms_thread_msg_new
from /opt/garnome-svn-2.28/lib/evolution/2.30/libevolution-mail.so.0
#6 camel_session_thread_msg_new
from /opt/garnome-svn-2.28/lib/libcamel-provider-1.2.so.14
#7 folder_changed_base
from /opt/garnome-svn-2.28/lib/libcamel-provider-1.2.so.14
#8 folder_changed
from /opt/garnome-svn-2.28/lib/libcamel-provider-1.2.so.14
#9 camel_object_trigger_event
from /opt/garnome-svn-2.28/lib/libcamel-1.2.so.14
#10 local_refresh_info
from /opt/garnome-svn-2.28/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#11 camel_folder_refresh_info
from /opt/garnome-svn-2.28/lib/libcamel-provider-1.2.so.14
#12 refresh_folder_exec
from /opt/garnome-svn-2.28/lib/evolution/2.30/libevolution-mail.so.0
#13 mail_msg_proxy
from /opt/garnome-svn-2.28/lib/evolution/2.30/libevolution-mail.so.0
#14 g_thread_pool_thread_proxy
from /opt/garnome-svn-2.28/lib/libglib-2.0.so.0
#15 g_thread_create_proxy
from /opt/garnome-svn-2.28/lib/libglib-2.0.so.0
#16 start_thread
from //lib/libpthread.so.0
#17 clone
from //lib/libc.so.6

Comment 1 Akhil Laddha 2010-02-01 03:18:27 UTC

could be a dup of bug 608637 , traces are different after 6 lines from local_refresh_info

David, traces don't have line numbers. Do you debug packages installed ? 

Could you please provide better traces in case you get crash again, thanks.

Comment 2 Akhil Laddha 2010-03-03 06:31:06 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!