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


Summary:	crash in Tasks:


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-10-23 21:32 UTC by jgajek
Modified:	2007-10-24 20:18 UTC

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

Description jgajek 2007-10-23 21:32:34 UTC

Version: 2.10

What were you doing when the application 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 138866688 vsize: 138866688 resident: 39096320 share: 29478912 rss: 39096320 rss_rlim: 4294967295
CPU usage: start_time: 1193175137 rtime: 244 utime: 206 stime: 38 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208805664 (LWP 3027)]
[New Thread -1297093744 (LWP 3077)]
[New Thread -1247810672 (LWP 3052)]
[New Thread -1224799344 (LWP 3048)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 172359

Thread 4 (Thread -1224799344 (LWP 3048))

#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 camel_filter_driver_filter_message
from /usr/lib/libcamel-provider-1.2.so.10
#15 camel_filter_driver_filter_folder
from /usr/lib/libcamel-provider-1.2.so.10
#16 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#17 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#18 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#19 ??
from /lib/libglib-2.0.so.0
#20 ??
from /lib/libglib-2.0.so.0
#21 start_thread
from /lib/libpthread.so.0
#22 clone
from /lib/libc.so.6



----------- .xsession-errors (8 sec old) ---------------------
localuser:jgajek being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2733
** (gnome-session:2733): WARNING **: Host name lookup failure on localhost.
error getting update info:  Cannot retrieve repository metadata (repomd.xml) for repository: atrpms. Please verify its path and try again
** Message: <info>  You are now connected to the wireless network 'AP1910'.
CalDAV Eplugin starting up ...
** (evolution:3027): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3027): DEBUG: mailto URL program: evolution
--------------------------------------------------

Comment 1 Tobias Mueller 2007-10-24 20:18:40 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 ***