Bug 503833 – crash in 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 503833 - crash in Email:


Summary:	crash in Email:


Status:	RESOLVED DUPLICATE of bug 339602

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-12-16 11:25 UTC by jameling
Modified:	2007-12-16 17:33 UTC

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

Description jameling 2007-12-16 11:25:11 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.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 213934080 vsize: 213934080 resident: 63467520 share: 45355008 rss: 63467520 rss_rlim: 4294967295
CPU usage: start_time: 1197804230 rtime: 1177 utime: 951 stime: 226 cutime:1 cstime: 4 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 -1209076000 (LWP 3352)]
[New Thread -1301369968 (LWP 3414)]
[New Thread -1269498992 (LWP 3379)]
[New Thread -1259009136 (LWP 3374)]
[New Thread -1248519280 (LWP 3373)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 182007

Thread 5 (Thread -1248519280 (LWP 3373))

#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 (13 sec old) ---------------------
(evolution:3352): camel-WARNING **: Could not find key entry for word 'rs232週邊變成usb隨插即用': 不適用的引數
(evolution:3352): camel-WARNING **: Could not find key entry for word '週邊變成usb隨插即用': 不適用的引數
(evolution:3352): camel-WARNING **: Could not find key entry for word 'rs232週邊變成usb隨插即用': 不適用的引數
(evolution:3352): camel-WARNING **: Could not find key entry for word '週邊變成usb隨插即用': 不適用的引數
(bug-buddy:3417): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: 第 1 行第 40 個字發生錯誤：元素‘b’已關閉，但開啟中的元素是‘span’
--------------------------------------------------

Comment 1 Susana 2007-12-16 17:33:09 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 ***