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 413434 - evolution still crashes after application startup
evolution still crashes after application startup
Status: RESOLVED DUPLICATE of bug 371529
Product: evolution
Classification: Applications
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-03-01 13:38 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-03-01 13:36:52 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 after application startup
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
This happens mostly but not continuously.
The application worked for a few days but now the problem arises again.
I didn't change anything in my environment.

Steps to reproduce the crash:
1.  see attached debug output
2. 
3. 

Expected Results: The Application shouldn't crash


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 19175)]
[New Thread 1126455616 (LWP 19202)]
[New Thread 1115965760 (LWP 19201)]
[New Thread 1105475904 (LWP 19198)]
[New Thread 1094719808 (LWP 19197)]
[New Thread 1094986048 (LWP 19195)]
[New Thread 1084229952 (LWP 19193)]
(no debugging symbols found)
0x000000362410ccef in waitpid () from /lib64/libpthread.so.0

Thread 2 (Thread 1126455616 (LWP 19202))

  • #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-01 13:38 -------

Comment 1 André Klapper 2007-03-04 23:02:26 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. Could you please install some debugging packages [1], start the application as normal, 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 in advance!

[1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 André Klapper 2007-04-03 00:54:44 UTC
Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue.

For some yet unknown reason, such stacktraces are pretty common currently on certain distributions. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue.

Just in case you ever can reproduce this crash later, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace.  Thanks!

Closing this bug report as no further information has been provided.
Comment 3 André Klapper 2007-06-11 09:26:09 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 ***