Bug 445383 – crash in Evolution Mail: was starting up evolutio...

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 445383 - crash in Evolution Mail: was starting up evolutio...


Summary:	crash in Evolution Mail: was starting up evolutio...


Status:	RESOLVED DUPLICATE of bug 371529

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-06-08 06:42 UTC by Weber_Stephan
Modified:	2007-06-11 09:19 UTC

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

Description Weber_Stephan 2007-06-08 06:42:23 UTC

What were you doing when the application crashed?
was starting up evolution; message of evolution says: storing folder (45% complete)

before:
had a spaceproblem before (no space left on device); 
created space; 
restartet evolution ....


Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.20 #5 SMP Sat May 26 15:43:18 CEST 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: 83927040 vsize: 83927040 resident: 25673728 share: 14893056 rss: 25673728 rss_rlim: 4294967295
CPU usage: start_time: 1181284731 rtime: 766 utime: 560 stime: 206 cutime:25 cstime: 2 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232557472 (LWP 6493)]
[New Thread -1272980592 (LWP 6884)]
[New Thread -1264587888 (LWP 6858)]
[New Thread -1256195184 (LWP 6857)]
[New Thread -1245566064 (LWP 6799)]
[New Thread -1253979248 (LWP 6758)]
[New Thread -1237001328 (LWP 6749)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 139280

Thread 3 (Thread -1264587888 (LWP 6858))

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



----------- .xsession-errors ---------------------
kbuildsycoca: WARNING: '/usr/share/applications/iceweasel.desktop' specifies undefined mimetype/servicetype 'application/rdf+xml'
kbuildsycoca: WARNING: '/usr/share/applications/vmware-workstation.desktop' specifies undefined mimetype/servicetype 'application/x-vmware-vm'
kbuildsycoca: WARNING: '/usr/share/applications/vmware-workstation.desktop' specifies undefined mimetype/servicetype 'application/x-vmware-team'
(evolution:6493): camel-WARNING **: Could not find key entry for word 'mzhd0chvk50jp20onx0fq': Success
(evolution:6493): camel-WARNING **: Could not find key entry for word 'mb5a0chvk50jp20onx0fc': Success
(evolution:6493): camel-WARNING **: Could not find key entry for word 'mb5a0chvk50jp208uw0fr': Success
(evolution:6493): camel-WARNING **: Could not find key entry for word 'mb5a0chvk50jp206sy0fp': Success
--------------------------------------------------

Comment 1 André Klapper 2007-06-11 09:19:15 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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