Bug 498903 – crash in Tasks: My processor was running...

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 498903 - crash in Tasks: My processor was running...


Summary:	crash in Tasks: My processor was running...


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-22 05:05 UTC by deathstar550
Modified:	2007-11-22 14:29 UTC

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

Description deathstar550 2007-11-22 05:05:30 UTC

Version: 2.10

What were you doing when the application crashed?
My processor was running on full load (IBM's systemsim, firefox, pidgin). I opened Evolution to check my email and it crashed while retrieving my inbox.  


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.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: 143577088 vsize: 143577088 resident: 48816128 share: 33161216 rss: 48816128 rss_rlim: 4294967295
CPU usage: start_time: 1195707763 rtime: 464 utime: 418 stime: 46 cutime:30 cstime: 5 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 -1208989984 (LWP 3474)]
[New Thread -1260852336 (LWP 3509)]
[New Thread -1301566576 (LWP 3501)]
[New Thread -1290409072 (LWP 3500)]
[New Thread -1249969264 (LWP 3493)]
[New Thread -1228989552 (LWP 3490)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 179207

Thread 2 (Thread -1260852336 (LWP 3509))

#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_get_message
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 (12 sec old) ---------------------
(evolution:3474): camel-WARNING **: Could not find key entry for word '0xc000000000047b48': Success
(evolution:3474): camel-WARNING **: Could not find key entry for word '0xc000000000047b48': Success
(evolution:3474): camel-WARNING **: Could not find key entry for word '0x08000000': Success
(evolution:3474): camel-WARNING **: Could not find key entry for word '0x00000080': Success
(evolution:3474): camel-WARNING **: Could not find key entry for word '0x00000006': Success
--------------------------------------------------

Comment 1 Tobias Mueller 2007-11-22 14:29:00 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 ***