Bug 493991 – crash in Tasks: re-opening evolution aft...

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 493991 - crash in Tasks: re-opening evolution aft...


Summary:	crash in Tasks: re-opening evolution aft...


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-11-06 02:39 UTC by it
Modified:	2007-11-07 21:55 UTC

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

Description it 2007-11-06 02:39:59 UTC

Version: 2.10

What were you doing when the application crashed?
re-opening evolution after have deleted *.ev-summary files


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.18-8.1.15.el5xen #1 SMP Mon Oct 22 09:01:12 EDT 2007 x86_64
X Vendor: The XFree86 Project, Inc
X Vendor Release: 40300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 719712256 vsize: 719712256 resident: 51609600 share: 35520512 rss: 51609600 rss_rlim: 18446744073709551615
CPU usage: start_time: 1194316717 rtime: 163 utime: 126 stime: 37 cutime:0 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496390288 (LWP 13637)]
[New Thread 1147435344 (LWP 13669)]
[New Thread 1115699536 (LWP 13663)]
[New Thread 1094719824 (LWP 13662)]
[New Thread 1126455632 (LWP 13660)]
[New Thread 1084229968 (LWP 13654)]
(no debugging symbols found)
0x0000003e39a0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 175605

Thread 6 (Thread 1084229968 (LWP 13654))

#0 __lll_mutex_lock_wait
from /lib64/libpthread.so.0
#1 _L_mutex_lock_103
from /lib64/libpthread.so.0
#2 pthread_mutex_lock
from /lib64/libpthread.so.0
#3 <signal handler called>
#4 camel_index_add_name
from /usr/lib64/libcamel-1.2.so.10
#5 camel_folder_summary_info_new_from_parser
from /usr/lib64/libcamel-provider-1.2.so.10
#6 camel_folder_summary_add_from_parser
from /usr/lib64/libcamel-provider-1.2.so.10
#7 ??
from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamellocal.so
#8 ??
from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamellocal.so
#9 ??
from /usr/lib64/evolution-data-server-1.2/camel-providers/libcamellocal.so
#10 camel_folder_append_message
from /usr/lib64/libcamel-provider-1.2.so.10
#11 camel_filter_driver_filter_message
from /usr/lib64/libcamel-provider-1.2.so.10
#12 camel_filter_driver_filter_folder
from /usr/lib64/libcamel-provider-1.2.so.10
#13 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#14 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#15 ??
from /usr/lib64/evolution/2.10/components/libevolution-mail.so
#16 ??
from /lib64/libglib-2.0.so.0
#17 ??
from /lib64/libglib-2.0.so.0
#18 start_thread
from /lib64/libpthread.so.0
#19 clone
from /lib64/libc.so.6

Comment 1 Tobias Mueller 2007-11-07 21:55:38 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 ***