Bug 357947 – Evolution crashed

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 357947 - Evolution crashed


Summary:	Evolution crashed


Status:	RESOLVED DUPLICATE of bug 339602

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:	2006-09-27 10:50 UTC by Gulliver
Modified:	2007-07-26 21:46 UTC

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

Description Gulliver 2006-09-27 10:49:31 UTC

Distribution: Ubuntu 6.06 (dapper)
Package: Evolution
Severity: critical
Version: GNOME2.14.3 2.6.x
Gnome-Distributor: Ubuntu
Synopsis: Evolution crashed
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.6.x
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 "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231906592 (LWP 1946)]
[New Thread -1332040784 (LWP 2775)]
[New Thread -1331381328 (LWP 1964)]
[New Thread -1322988624 (LWP 1963)]
[New Thread -1314595920 (LWP 1962)]
[New Thread -1306203216 (LWP 1960)]
[New Thread -1279861840 (LWP 1958)]
[New Thread -1271063632 (LWP 1953)]
[New Thread -1262634064 (LWP 1951)]
[New Thread -1254241360 (LWP 1950)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 73379

Thread 7 (Thread -1279861840 (LWP 1958))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/tls/i686/cmov/libpthread.so.0
#2 _L_mutex_lock_33
from /lib/tls/i686/cmov/libpthread.so.0
#3 ??
#4 ??
#5 ??
from /lib/tls/i686/cmov/libpthread.so.0
#6 ??
#7 ??
#8 ??
from /lib/tls/i686/cmov/libc.so.6
#9 pthread_mutex_init
from /lib/tls/i686/cmov/libc.so.6
#10 pthread_mutex_lock
from /lib/tls/i686/cmov/libc.so.6
#11 es_menu_hook_get_type
#12 <signal handler called>
#13 camel_index_add_name
from /usr/lib/libcamel-1.2.so.0
#14 camel_folder_summary_info_new_from_parser
from /usr/lib/libcamel-provider-1.2.so.8
#15 camel_folder_summary_add_from_parser
from /usr/lib/libcamel-provider-1.2.so.8
#16 camel_mbox_summary_sync_mbox
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#17 camel_mbox_summary_sync_mbox
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#18 camel_local_summary_check
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#19 camel_mbox_folder_new
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#20 camel_folder_get_message
from /usr/lib/libcamel-provider-1.2.so.8
#21 mail_empty_trash
from /usr/lib/evolution/2.6/components/libevolution-mail.so
#22 mail_enable_stop
from /usr/lib/evolution/2.6/components/libevolution-mail.so
#23 e_thread_busy
from /usr/lib/libedataserver-1.2.so.7
#24 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#25 clone
from /lib/tls/i686/cmov/libc.so.6





------- Bug created by bug-buddy at 2006-09-27 10:50 -------

Comment 1 Karsten Bräckelmann 2006-09-27 10:58:33 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Karsten Bräckelmann 2006-10-08 01:21:59 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 distros. 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.


Also, please feel free to report any further bugs you find.  Thanks!


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

Comment 3 André Klapper 2007-07-26 21:46:03 UTC


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