Bug 521039 – crash in Tasks: starting evolution

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 521039 - crash in Tasks: starting evolution


Summary:	crash in Tasks: starting evolution


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-03-07 17:46 UTC by ademir
Modified:	2008-03-07 21:49 UTC

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

Description ademir 2008-03-07 17:46:57 UTC

Version: 2.10

What were you doing when the application crashed?
starting evolution


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.21-6.fc7xen #1 SMP Mon Nov 19 07:14:27 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 148365312 vsize: 148365312 resident: 48005120 share: 32538624 rss: 48005120 rss_rlim: 4294967295
CPU usage: start_time: 1204912039 rtime: 1665 utime: 1179 stime: 486 cutime:58 cstime: 17 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208186128 (LWP 8141)]
[New Thread -1307968624 (LWP 8171)]
[New Thread -1295848560 (LWP 8165)]
[New Thread -1248859248 (LWP 8161)]
[New Thread -1226282096 (LWP 8158)]
(no debugging symbols found)
0x0097e402 in __kernel_vsyscall ()

+ Trace 191654

Thread 3 (Thread -1295848560 (LWP 8165))

#0 __kernel_vsyscall
#1 __lll_lock_wait
from /lib/i686/nosegneg/libpthread.so.0
#2 _L_lock_88
from /lib/i686/nosegneg/libpthread.so.0
#3 pthread_mutex_lock
from /lib/i686/nosegneg/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/i686/nosegneg/libpthread.so.0
#19 clone
from /lib/i686/nosegneg/libc.so.6



----------- .xsession-errors (10 sec old) ---------------------
(evolution:8141): camel-WARNING **: Could not find key entry for word '180206000012007oc00066': Multibyte ou caracter largo inválido
(evolution:8141): camel-WARNING **: Could not find key entry for word '180206000012007oc00067': Multibyte ou caracter largo inválido
(evolution:8141): camel-WARNING **: Could not find key entry for word '180206000012007oc00066': Multibyte ou caracter largo inválido
(evolution:8141): camel-WARNING **: Could not find key entry for word '180206000012007oc00067': Multibyte ou caracter largo inválido
(evolution:8141): camel-WARNING **: Could not find key entry for word '10000000000000000000000000000000000': Multibyte ou caracter largo inválido
--------------------------------------------------

Comment 1 Tobias Mueller 2008-03-07 21:49:27 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 ***