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


Summary:	crash in Tasks:


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-17 00:28 UTC by jgajek
Modified:	2007-08-17 08:40 UTC

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

Description jgajek 2007-08-17 00:28:15 UTC

Version: 2.10

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 136650752 vsize: 136650752 resident: 36036608 share: 28864512 rss: 36036608 rss_rlim: 4294967295
CPU usage: start_time: 1183779558 rtime: 112 utime: 97 stime: 15 cutime:1 cstime: 3 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 -1208985888 (LWP 2480)]
[New Thread -1304257648 (LWP 2509)]
[New Thread -1245934704 (LWP 2502)]
[New Thread -1224954992 (LWP 2499)]
(no debugging symbols found)
0x0013c402 in __kernel_vsyscall ()

+ Trace 155805

Thread 2 (Thread -1304257648 (LWP 2509))

#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 ---------------------
** (gnome-session:2024): WARNING **: Host name lookup failure on localhost.
error getting update info:  Cannot open/read repomd.xml file for repository: atrpms
** Message: <info>  You are now connected to the wireless network 'AP1910'.
CalDAV Eplugin starting up ...
** (evolution:2357): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2357): DEBUG: mailto URL program: evolution
CalDAV Eplugin starting up ...
** (evolution:2427): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2427): DEBUG: mailto URL program: evolution
Loading "installonlyn" plugin
CalDAV Eplugin starting up ...
** (evolution:2480): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2480): DEBUG: mailto URL program: evolution
--------------------------------------------------

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