Bug 511115 – crash in Tasks: initial start up of Evol...

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 511115 - crash in Tasks: initial start up of Evol...


Summary:	crash in Tasks: initial start up of Evol...


Status:	RESOLVED DUPLICATE of bug 339602

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-21 20:29 UTC by Todd Robinson
Modified:	2008-01-22 12:11 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Todd Robinson 2008-01-21 20:29:03 UTC

What were you doing when the application crashed?
initial start up of Evolution, displayed folders, list of e-mails, but no detail. status at bottom indicates Storing folder (6% complete).


Distribution: Fedora release 6.92 (Rawhide)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3084.fc7 #1 SMP Tue Apr 17 17:18:51 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 281341952 vsize: 281341952 resident: 120725504 share: 16072704 rss: 120725504 rss_rlim: 4294967295
CPU usage: start_time: 1200947193 rtime: 3678 utime: 2649 stime: 1029 cutime:108 cstime: 58 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208486176 (LWP 1422)]
[New Thread -1427113072 (LWP 1485)]
[New Thread -1329615984 (LWP 1463)]
[New Thread -1275081840 (LWP 1456)]
[New Thread -1298146416 (LWP 1452)]
[New Thread -1277166704 (LWP 1449)]
[New Thread -1254102128 (LWP 1447)]
[New Thread -1231889520 (LWP 1445)]
(no debugging symbols found)
0x00d4f402 in __kernel_vsyscall ()

+ Trace 186246

Thread 5 (Thread -1298146416 (LWP 1452))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 camel_index_add_name
from /usr/lib/libcamel-1.2.so.10
#7 camel_folder_summary_info_new_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#8 camel_folder_summary_add_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#9 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#10 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#11 camel_local_summary_check
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#12 ??
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#13 camel_folder_append_message
from /usr/lib/libcamel-provider-1.2.so.10
#14 ??
from /usr/lib/libcamel-provider-1.2.so.10
#15 e_sexp_term_eval
from /usr/lib/libedataserver-1.2.so.9
#16 ??
from /usr/lib/libedataserver-1.2.so.9
#17 e_sexp_term_eval
from /usr/lib/libedataserver-1.2.so.9
#18 e_sexp_eval
from /usr/lib/libedataserver-1.2.so.9
#19 camel_filter_driver_filter_message
from /usr/lib/libcamel-provider-1.2.so.10
#20 camel_filter_driver_filter_folder
from /usr/lib/libcamel-provider-1.2.so.10
#21 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#22 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#23 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#24 ??
from /lib/libglib-2.0.so.0
#25 ??
from /lib/libglib-2.0.so.0
#26 start_thread
from /lib/libpthread.so.0
#27 clone
from /lib/libc.so.6

Comment 1 Tobias Mueller 2008-01-22 12:11:28 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 339602 ***