GNOME Bugzilla – Bug 374646
Crash when starting Evolution
Last modified: 2007-08-18 15:24:18 UTC
Distribution: Gentoo Base System version 1.12.6 Package: Evolution Severity: Normal Version: GNOME2.14.2 unspecified Gnome-Distributor: Gentoo Synopsis: Crash when starting Evolution Bugzilla-Product: Evolution Bugzilla-Component: Mailer Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: I just restarted Evolution after ahving recieved a lot of new mail. The new mail was still unread. Steps to reproduce the crash: 1. Start Evolution 2. <boom> 3. Expected Results: No boom How often does this happen? This is the only such event Additional Information: I' sorry for the rather unhelpful description of how the error came about, but it seems that some indexing code is the culprit. Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.6' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47342810987056 (LWP 14371)] [New Thread 1098918224 (LWP 14401)] [New Thread 1107310928 (LWP 14382)] [New Thread 1115703632 (LWP 14381)] [New Thread 1090525520 (LWP 14377)] [New Thread 1082132816 (LWP 14376)] 0x00002b0ed84b292f in waitpid () from /lib/libpthread.so.0
+ Trace 86037
Thread 1 (Thread 47342810987056 (LWP 14371))
------- Bug created by bug-buddy at 2006-11-13 11:29 -------
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!
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!
https://launchpad.net/ubuntu/+source/evolution/+bug/97543 has a similar backtrace.
+ Trace 123272
this is most likely the same issue as bug 371586 *** This bug has been marked as a duplicate of 371586 ***