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


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 339602

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-30 11:43 UTC by ruib
Modified:	2008-01-30 23:14 UTC

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

Description ruib 2008-01-30 11:43:19 UTC

Version: 2.10

What were you doing when the application crashed?



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.23.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 143134720 vsize: 143134720 resident: 42373120 share: 31989760 rss: 42373120 rss_rlim: 4294967295
CPU usage: start_time: 1201693330 rtime: 298 utime: 231 stime: 67 cutime:34 cstime: 7 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 -1208445216 (LWP 3373)]
[New Thread -1296266352 (LWP 3390)]
[New Thread -1270137968 (LWP 3383)]
[New Thread -1248859248 (LWP 3380)]
[New Thread -1225933936 (LWP 3376)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 187375

Thread 2 (Thread -1296266352 (LWP 3390))

#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 (16 sec old) ---------------------
alarm-notify.c:316 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:1998 (alarm_queue_add_async) - 0x868c3b0
alarm-queue.c:585 (load_alarms_for_today) - From Wed Jan 30 11:40:18 2008
 to Wed Jan 30 11:40:18 2008
alarm-queue.c:522 (load_alarms) 
alarm-queue.c:551 (load_alarms)restoring session
--- Hash table keys for warning below:
--> file:///home/ruib
(nautilus:3367): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
CalDAV Eplugin starting up ...
** (evolution:3373): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3373): DEBUG: mailto URL program: evolution
--------------------------------------------------

Comment 1 Tobias Mueller 2008-01-30 23:14:56 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 ***