Bug 401009 – crash in Evolution: Opening again...

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 401009 - crash in Evolution: Opening again...


Summary:	crash in Evolution: Opening again...


Status:	RESOLVED DUPLICATE of bug 371529

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.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-01-26 13:55 UTC by matchb00k090
Modified:	2007-01-27 13:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description matchb00k090 2007-01-26 13:55:20 UTC

What were you doing when the application crashed?
Opening again...


Distribution: Slackware Slackware 11.0.0
Gnome Release: 2.16.2 2006-11-22 (Dropline GNOME)
BugBuddy Version: 2.16.0

Memory status: size: 117891072 vsize: 0 resident: 117891072 share: 0 rss: 24842240 rss_rlim: 0
CPU usage: start_time: 1169819720 rtime: 0 utime: 276 stime: 0 cutime:240 cstime: 0 timeout: 36 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1233545536 (LWP 3512)]
[New Thread -1318683728 (LWP 3529)]
[New Thread -1310295120 (LWP 3528)]
[New Thread -1301906512 (LWP 3527)]
[New Thread -1283458128 (LWP 3526)]
[New Thread -1258292304 (LWP 3524)]
[New Thread -1275069520 (LWP 3523)]
[New Thread -1266680912 (LWP 3520)]
[New Thread -1248449616 (LWP 3518)]
0xb6a23071 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 105423

Thread 3 (Thread -1310295120 (LWP 3528))

#0 __lll_mutex_lock_wait
from /lib/tls/libpthread.so.0
#1 _L_mutex_lock_33
from /lib/tls/libpthread.so.0
#2 ??
#3 es_menu_hook_get_type
#4 <signal handler called>
#5 camel_index_add_name
from /usr/lib/libcamel-1.2.so.0
#6 camel_folder_summary_info_new_from_parser
from /usr/lib/libcamel-provider-1.2.so.8
#7 camel_folder_summary_add_from_parser
from /usr/lib/libcamel-provider-1.2.so.8
#8 camel_mbox_summary_xstatus
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#9 camel_mbox_summary_xstatus
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#10 camel_local_summary_check
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#11 camel_local_folder_lock
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#12 camel_folder_refresh_info
from /usr/lib/libcamel-provider-1.2.so.8
#13 mail_sync_store
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#14 mail_enable_stop
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#15 e_thread_busy
from /usr/lib/libedataserver-1.2.so.7
#16 start_thread
from /lib/tls/libpthread.so.0
#17 clone
from /lib/tls/libc.so.6

Comment 1 palfrey 2007-01-27 13:31:28 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 ***