Bug 487971 – crash in Tasks:

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 487971 - crash in Tasks:


Summary:	crash in Tasks:


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:	2007-10-18 17:20 UTC by n.weekes
Modified:	2007-10-23 01:05 UTC

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

Description n.weekes 2007-10-18 17:20:48 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 136392704 vsize: 136392704 resident: 41140224 share: 30441472 rss: 41140224 rss_rlim: 4294967295
CPU usage: start_time: 1192728039 rtime: 160 utime: 135 stime: 25 cutime:0 cstime: 1 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 -1209112864 (LWP 6369)]
[New Thread -1265673328 (LWP 6391)]
[New Thread -1244300400 (LWP 6389)]
[New Thread -1223320688 (LWP 6386)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 171183

Thread 2 (Thread -1265673328 (LWP 6391))

#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_refresh_info
from /usr/lib/libcamel-provider-1.2.so.10
#14 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#15 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#16 ??
from /lib/libglib-2.0.so.0
#17 ??
from /lib/libglib-2.0.so.0
#18 start_thread
from /lib/libpthread.so.0
#19 clone
from /lib/libc.so.6



----------- .xsession-errors ---------------------
(evolution:6369): camel-WARNING **: Could not find key entry for word 'm8reytesxcqsvgfoej0tfyi9lw8j3lxr8uv': Success
(evolution:6369): camel-WARNING **: Could not find key entry for word '22pt77rdznjnhdwtxzu0g8tmks': Success
(evolution:6369): camel-WARNING **: Could not find key entry for word 'cfqivpfv9ypk7x2px6t5b2ep': Success
(evolution:6369): camel-WARNING **: Could not find key entry for word 'kqcafsbxwb3pmedcskw18a31tpbdp4ftl': Success
(evolution:6369): camel-WARNING **: Could not find key entry for word '6cotlwo9x0v7frxw0j8sg2i0k2e56h5tq': Success
--------------------------------------------------

Comment 1 Tobias Mueller 2007-10-23 01:05:32 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 ***