Bug 515440 – 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 515440 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 339602

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.10.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:	2008-02-09 17:18 UTC by david.schornack
Modified:	2008-02-09 20:18 UTC

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

Description david.schornack 2008-02-09 17:18:01 UTC

Version: 2.10

What were you doing when the application crashed?



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

System: Linux 2.6.23.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 150392832 vsize: 150392832 resident: 43986944 share: 32534528 rss: 43986944 rss_rlim: 4294967295
CPU usage: start_time: 1202577462 rtime: 248 utime: 190 stime: 58 cutime:24 cstime: 3 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 -1208588576 (LWP 8241)]
[New Thread -1313576048 (LWP 8258)]
[New Thread -1313309808 (LWP 8256)]
[New Thread -1272984688 (LWP 8251)]
[New Thread -1229194352 (LWP 8246)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 188668

Thread 2 (Thread -1313576048 (LWP 8258))

#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 (10 sec old) ---------------------
(evolution:8241): camel-WARNING **: Could not find key entry for word 'e6b387e4c7a64110vgnvcm20000012281eac': Success
(evolution:8241): camel-WARNING **: Could not find key entry for word 'f1b38f17a7074110vgnvcm20000012281eac': Success
(evolution:8241): camel-WARNING **: Could not find key entry for word '4061730000000034': Invalid or incomplete multibyte or wide character
(evolution:8241): camel-WARNING **: Could not find key entry for word '4061730000000067': Invalid or incomplete multibyte or wide character
(evolution:8241): camel-WARNING **: Could not find key entry for word '4061730000000075': Invalid or incomplete multibyte or wide character
--------------------------------------------------

Comment 1 Tobias Mueller 2008-02-09 20:18:26 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 ***