Bug 464052 – crash in Tasks: i opened evolution and i...

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 464052 - crash in Tasks: i opened evolution and i...


Summary:	crash in Tasks: i opened evolution and i...


Status:	RESOLVED DUPLICATE of bug 339602

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-08-06 15:39 UTC by claudio
Modified:	2007-08-17 08:40 UTC

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

Description claudio 2007-08-06 15:39:54 UTC

Version: 2.10

What were you doing when the application crashed?
i opened evolution and it was archiving the messages and it got up to 13% and it crashed



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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 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: 123445248 vsize: 123445248 resident: 53862400 share: 28487680 rss: 53862400 rss_rlim: 4294967295
CPU usage: start_time: 1186414335 rtime: 1779 utime: 1652 stime: 127 cutime:3 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 -1209104672 (LWP 4645)]
[New Thread -1230378096 (LWP 4702)]
[New Thread -1251751024 (LWP 4701)]
[New Thread -1240867952 (LWP 4681)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 153237

Thread 2 (Thread -1230378096 (LWP 4702))

#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 (3318 sec old) ---------------------
(evolution:4000): camel-WARNING **: Could not create key entry for word 'training': Interrupted system call
(evolution:4000): camel-WARNING **: Could not create key entry for word 'tbd': Interrupted system call
(evolution:4000): camel-WARNING **: Could not create key entry for word 'workstation': Interrupted system call
(evolution:4000): camel-WARNING **: Could not create key entry for word 'croft': Interrupted system call
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2007-08-17 08:40:04 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 339602 ***