Bug 485781 – crash in Tasks: Reading mail.

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 485781 - crash in Tasks: Reading mail.


Summary:	crash in Tasks: Reading mail.


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-11 16:05 UTC by lemasaya
Modified:	2007-10-11 19:17 UTC

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

Description lemasaya 2007-10-11 16:05:09 UTC

Version: 2.10

What were you doing when the application crashed?
Reading mail.


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.20-2936.fc7xen #1 SMP Fri Sep 21 12:07:35 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: nuoveXT-1.6

Memory status: size: 123244544 vsize: 123244544 resident: 44179456 share: 29351936 rss: 44179456 rss_rlim: 4294967295
CPU usage: start_time: 1192118500 rtime: 694 utime: 506 stime: 188 cutime:191 cstime: 30 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208830240 (LWP 21813)]
[New Thread -1256559728 (LWP 21899)]
[New Thread -1281754224 (LWP 21889)]
[New Thread -1246069872 (LWP 21844)]
[New Thread -1224688752 (LWP 21840)]
(no debugging symbols found)
0x00da3402 in __kernel_vsyscall ()

+ Trace 169537

Thread 2 (Thread -1256559728 (LWP 21899))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/i686/nosegneg/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/i686/nosegneg/libpthread.so.0
#3 pthread_mutex_lock
from /lib/i686/nosegneg/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/i686/nosegneg/libpthread.so.0
#19 clone
from /lib/i686/nosegneg/libc.so.6



----------- .xsession-errors (43364 sec old) ---------------------
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Tobias Mueller 2007-10-11 19:17:50 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 ***