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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 371529

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
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-05-26 16:04 UTC by Ronald L. Peoples II
Modified:	2007-06-11 09:19 UTC

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

Description Ronald L. Peoples II 2007-05-26 16:04:01 UTC

What were you doing when the application crashed?



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

System: Linux 2.6.21-1.3190.fc7 #1 SMP Tue May 22 22:25:14 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: 124485632 vsize: 124485632 resident: 29208576 share: 18636800 rss: 29208576 rss_rlim: 4294967295
CPU usage: start_time: 1180195350 rtime: 345 utime: 310 stime: 35 cutime:1 cstime: 2 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 -1208502560 (LWP 3954)]
[New Thread -1310721136 (LWP 4085)]
[New Thread -1300231280 (LWP 4083)]
[New Thread -1211012208 (LWP 4054)]
[New Thread -1249334384 (LWP 4040)]
[New Thread -1227949168 (LWP 3976)]
(no debugging symbols found)
0x00e64402 in __kernel_vsyscall ()

+ Trace 136161

Thread 3 (Thread -1300231280 (LWP 4083))

#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 em_utils_selection_get_uidlist
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#16 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#17 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#18 ??
from /lib/libglib-2.0.so.0
#19 ??
from /lib/libglib-2.0.so.0
#20 start_thread
from /lib/libpthread.so.0
#21 clone
from /lib/libc.so.6



----------- .xsession-errors ---------------------
(evolution:3954): camel-WARNING **: Could not find key entry for word '800000000000000004': Success
(evolution:3954): camel-WARNING **: Could not find key entry for word '800000000000000007': Success
(evolution:3954): camel-WARNING **: Could not find key entry for word '700000000000000041': Success
(evolution:3954): camel-WARNING **: Could not find key entry for word '700000000000000042': Success
(evolution:3954): camel-WARNING **: Could not find key entry for word '700000000000000043': Success
--------------------------------------------------

Comment 1 Pedro Villavicencio 2007-05-26 17:03:55 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 André Klapper 2007-06-11 09:19:47 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 371529 ***