Bug 485164 – crash in Evolution: une recherche dans un do...

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 485164 - crash in Evolution: une recherche dans un do...


Summary:	crash in Evolution: une recherche dans un do...


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:	2007-10-09 19:43 UTC by eric.dubreuil
Modified:	2007-10-10 08:31 UTC

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

Description eric.dubreuil 2007-10-09 19:43:44 UTC

What were you doing when the application crashed?
une recherche dans un dossier qui me sert d'archive de mail (+ de 1000 mails)


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

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 568147968 vsize: 568147968 resident: 63631360 share: 21041152 rss: 63631360 rss_rlim: 18446744073709551615
CPU usage: start_time: 1191956259 rtime: 1632 utime: 1382 stime: 250 cutime:4375 cstime: 249 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution-2.10'

(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 0x2b2d27e6c860 (LWP 4366)]
[New Thread 0x43046950 (LWP 6382)]
[New Thread 0x42845950 (LWP 4434)]
[New Thread 0x42044950 (LWP 4433)]
[New Thread 0x41843950 (LWP 4398)]
[New Thread 0x41042950 (LWP 4396)]
[New Thread 0x41001950 (LWP 4395)]
[New Thread 0x40800950 (LWP 4392)]
(no debugging symbols found)
0x00002b2d1ff61c7f in waitpid () from /lib/libpthread.so.0

+ Trace 169093

Thread 3 (Thread 0x42845950 (LWP 4434))

#0 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#1 _L_mutex_lock_100
from /lib/libpthread.so.0
#2 pthread_mutex_lock
from /lib/libpthread.so.0
#3 <signal handler called>
#4 camel_index_add_name
from /usr/lib/libcamel-1.2.so.10
#5 camel_folder_summary_info_new_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#6 camel_folder_summary_add_from_parser
from /usr/lib/libcamel-provider-1.2.so.10
#7 ??
from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
#8 ??
from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
#9 ??
from /usr/lib/evolution-data-server-1.2/camel-providers-10/libcamellocal.so
#10 ??
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#11 ??
from /usr/lib/libedataserver-1.2.so.9
#12 start_thread
from /lib/libpthread.so.0
#13 clone
from /lib/libc.so.6
#14 ??



----------- .xsession-errors ---------------------
(evolution-2.10:4366): e-data-server-WARNING **: Could not open converter for 'iso-7952-7' to 'UTF-8' charset
(evolution-2.10:4366): e-data-server-WARNING **: Could not open converter for 'iso-4484-1' to 'UTF-8' charset
(evolution-2.10:4366): e-data-server-WARNING **: Could not open converter for 'iso-1663-8' to 'UTF-8' charset
(evolution-2.10:4366): e-data-server-WARNING **: Could not open converter for 'iso-2277-2' to 'UTF-8' charset
(evolution-2.10:4366): e-data-server-WARNING **: Could not open converter for 'iso-8535-7' to 'UTF-8' charset
(evolution-2.10:4366): e-data-server-WARNING **: Could not open converter for '%CHARSET' to 'UTF-8' charset
(evolution-2.10:4366): e-data-server-WARNING **: Could not open converter for 'iso-928-1' to 'UTF-8' charset
(evolution-2.10:4366): e-data-server-WARNING **: Could not open converter for 'iso-1796-6' to 'UTF-8' charset
--------------------------------------------------

Comment 1 Tobias Mueller 2007-10-10 08:31:17 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 ***