Bug 405234 – evolution crashes again at startup

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 405234 - evolution crashes again at startup


Summary:	evolution crashes again at startup


Status:	RESOLVED DUPLICATE of bug 371529

Product:	evolution
Classification:	Applications
Component:	Calendar
Version:	2.6.x (obsolete)
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-07 05:12 UTC by Adi Treiner
Modified:	2007-06-11 09:26 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description Adi Treiner 2007-02-07 05:10:46 UTC

Distribution: Fedora Core release 5 (Bordeaux)
Package: Evolution
Severity: Normal
Version: GNOME2.14.3 2.6.x
Gnome-Distributor: Red Hat, Inc
Synopsis: evolution crashes again at startup
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
since today, evolution crashes again at startup. it work rather stable
for one week but now it crashes again. The only thing what has been
changed on my system was that I installed yesterday a language package
for open office.

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496391472 (LWP 14076)]
[New Thread 1126455616 (LWP 14105)]
[New Thread 1115965760 (LWP 14104)]
[New Thread 1105475904 (LWP 14098)]
[New Thread 1094719808 (LWP 14097)]
[New Thread 1094986048 (LWP 14095)]
[New Thread 1084229952 (LWP 14093)]
(no debugging symbols found)
0x000000362410ccef in waitpid () from /lib64/libpthread.so.0

+ Trace 108645

Thread 2 (Thread 1126455616 (LWP 14105))

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





------- Bug created by bug-buddy at 2007-02-07 05:12 -------

Comment 1 Kjartan Maraas 2007-02-07 18:20:58 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. Thanks in advance!

Comment 2 Bruno Boaventura 2007-03-09 21:52:30 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!

Comment 3 André Klapper 2007-06-11 09:26:18 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 ***