Bug 450673 – crash in Tasks: importando email do thun...

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 450673 - crash in Tasks: importando email do thun...


Summary:	crash in Tasks: importando email do thun...


Status:	RESOLVED DUPLICATE of bug 339602

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
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-06-24 17:16 UTC by efepimenta
Modified:	2007-07-26 21:48 UTC

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

Description efepimenta 2007-06-24 17:16:20 UTC

Version: 2.10

What were you doing when the application crashed?
importando email do thunderbird


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 224063488 vsize: 224063488 resident: 141467648 share: 37572608 rss: 141467648 rss_rlim: 4294967295
CPU usage: start_time: 1182705276 rtime: 5070 utime: 4213 stime: 857 cutime:3 cstime: 7 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 -1209108768 (LWP 3319)]
[New Thread -1221239920 (LWP 3389)]
[New Thread -1263223920 (LWP 3386)]
[New Thread -1252729968 (LWP 3382)]
[New Thread -1273709680 (LWP 3359)]
(no debugging symbols found)
0x00604402 in __kernel_vsyscall ()

+ Trace 143386

Thread 4 (Thread -1252729968 (LWP 3382))

#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_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/libpthread.so.0
#19 clone
from /lib/libc.so.6



----------- .xsession-errors (22 sec old) ---------------------
(evolution:3319): camel-WARNING **: Could not find key entry for word '0010000011000': Multibyte ou caracter largo inválido
(evolution:3319): camel-WARNING **: Could not find key entry for word 'hermética': Multibyte ou caracter largo inválido
(evolution:3319): camel-WARNING **: Could not find key entry for word 'hermética': Multibyte ou caracter largo inválido
(evolution:3319): camel-WARNING **: Could not find key entry for word 'bbb228808aeff7c8e1c2dbfae0874851': Multibyte ou caracter largo inválido
(evolution:3319): camel-WARNING **: Could not find key entry for word 'bbb228808aeff7c8e1c2dbfae0874851': Multibyte ou caracter largo inválido
--------------------------------------------------

Comment 1 palfrey 2007-06-25 00:12:55 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so and
reopen this bug or report a new one. Thanks in advance!

Comment 2 André Klapper 2007-07-26 21:48:16 UTC


*** This bug has been marked as a duplicate of 339602 ***