Bug 516588 – crash in Calendar: receiving email

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 516588 - crash in Calendar: receiving email


Summary:	crash in Calendar: receiving email


Status:	RESOLVED DUPLICATE of bug 339602

Product:	evolution
Classification:	Applications
Component:	Calendar
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:	2008-02-15 01:21 UTC by xianjimli
Modified:	2008-02-15 02:59 UTC

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

Description xianjimli 2008-02-15 01:21:22 UTC

What were you doing when the application crashed?
receiving email


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 169177088 vsize: 169177088 resident: 45920256 share: 19755008 rss: 45920256 rss_rlim: 4294967295
CPU usage: start_time: 1203038283 rtime: 1916 utime: 1309 stime: 607 cutime:0 cstime: 0 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 -1208813856 (LWP 3420)]
[New Thread -1274758256 (LWP 3445)]
[New Thread -1264268400 (LWP 3431)]
[New Thread -1264002160 (LWP 3430)]
[New Thread -1232131184 (LWP 3425)]
[New Thread -1221641328 (LWP 3424)]
(no debugging symbols found)
0x00794402 in __kernel_vsyscall ()

+ Trace 189255

Thread 6 (Thread -1221641328 (LWP 3424))

#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 (42 sec old) ---------------------
(evolution:3420): camel-WARNING **: Could not find key entry for word '15937680000': 无效的参数
(evolution:3420): camel-WARNING **: Could not find key entry for word '13753190000': 无效的参数
(evolution:3420): camel-WARNING **: Could not find key entry for word '13558940000': 无效的参数
(evolution:3420): camel-WARNING **: Could not find key entry for word '13358980000': 无效的参数
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Tobias Mueller 2008-02-15 02:59:23 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 ***