Bug 417756 – evolution still crashes at application 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 417756 - evolution still crashes at application startup


Summary:	evolution still crashes at application startup


Status:	RESOLVED DUPLICATE of bug 371529

Product:	evolution
Classification:	Applications
Component:	general
Version:	unspecified
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-13 05:47 UTC by Adi Treiner
Modified:	2007-06-11 09:23 UTC

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

Description Adi Treiner 2007-03-13 05:45:54 UTC

Distribution: Fedora Core release 5 (Bordeaux)
Package: Evolution
Severity: normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: evolution still crashes at application startup
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:


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 46912505486880 (LWP 4487)]
[New Thread 1126455616 (LWP 4652)]
[New Thread 1115965760 (LWP 4651)]
[New Thread 1105475904 (LWP 4593)]
[New Thread 1105209664 (LWP 4592)]
[New Thread 1094719808 (LWP 4590)]
[New Thread 1084229952 (LWP 4587)]
(no debugging symbols found)
0x000000362410ccef in waitpid () from /lib64/libpthread.so.0

+ Trace 118201

Thread 2 (Thread 1126455616 (LWP 4652))

#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-03-13 05:48 -------

Comment 1 Akhil Laddha 2007-03-13 14:12:57 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the "details", now
containing way more information. Please copy that stacktrace and paste it as a
comment here.  Thanks!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions

Comment 2 Bruno Boaventura 2007-04-15 12:02:03 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:23:57 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 ***