Bug 507175 – crash in Evolution Mail: sign

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 507175 - crash in Evolution Mail: sign


Summary:	crash in Evolution Mail: sign


Status:	RESOLVED DUPLICATE of bug 339602

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.10.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-04 03:18 UTC by zhao_yi
Modified:	2008-01-04 10:19 UTC

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

Description zhao_yi 2008-01-04 03:18:07 UTC

What were you doing when the application crashed?
sign



Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-1-686 #1 SMP Sat May 26 16:14:59 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 133541888 vsize: 133541888 resident: 48459776 share: 19046400 rss: 48459776 rss_rlim: 4294967295
CPU usage: start_time: 1199416587 rtime: 2342 utime: 2025 stime: 317 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 -1232927056 (LWP 4945)]
[New Thread -1293694064 (LWP 4957)]
[New Thread -1285305456 (LWP 4956)]
[New Thread -1285043312 (LWP 4955)]
[New Thread -1276535920 (LWP 4954)]
[New Thread -1257546864 (LWP 4952)]
[New Thread -1249158256 (LWP 4951)]
[New Thread -1240732784 (LWP 4948)]
(no debugging symbols found)
0xb778bbf1 in ?? () from /lib/libpthread.so.0

+ Trace 184002

Thread 2 (Thread -1293694064 (LWP 4957))

#0 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#1 _L_mutex_lock_86
from /lib/libpthread.so.0
#2 pthread_mutex_lock
from /lib/libpthread.so.0
#3 ??
#4 ??
#5 ??
#6 ??
#7 ??
#8 ??
from /usr/lib/libcamel-provider-1.2.so.10
#9 ??
#10 ??
#11 <signal handler called>
#12 camel_index_add_name
from /usr/lib/libcamel-1.2.so.10
#13 camel_folder_summary_info_new_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#14 camel_folder_summary_add_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#15 ??
from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
#16 ??
#17 ??
#18 ??



----------- .xsession-errors (57 sec old) ---------------------
(evolution:4945): camel-WARNING **: Could not find key entry for word '??????????47?': Invalid or incomplete multibyte or wide character
(evolution:4945): camel-WARNING **: Could not find key entry for word '????????????': Invalid argument
(evolution:4945): camel-WARNING **: Could not find key entry for word '??????': Invalid or incomplete multibyte or wide character
(evolution:4945): camel-WARNING **: Could not find key entry for word '??????????': Invalid or incomplete multibyte or wide character
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Tobias Mueller 2008-01-04 10:19:54 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 ***