GNOME Bugzilla – Bug 396769
evolution crashes while reading emails
Last modified: 2007-06-19 09:54:08 UTC
Distribution: Debian GNU/Linux "etch" Package: Evolution Severity: Normal Version: GNOME2.14.3 2.6.3 Gnome-Distributor: Debian Synopsis: evolution crash while reading emails Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Bugzilla-Version: 2.6.3 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: it hangs and a new window pop up asking for restart/close/notify. If I restart the application than it crash again just after displaying the message list. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? once or twice a day Additional Information: If I restart evolution and quickly change to a different IMAP folder, then it does not hangs. 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 -1231796544 (LWP 10685)] [New Thread -1299137616 (LWP 10698)] [New Thread -1282241616 (LWP 10695)] [New Thread -1273578576 (LWP 10693)] [New Thread -1265185872 (LWP 10690)] [New Thread -1255646288 (LWP 10689)] [New Thread -1247253584 (LWP 10687)] [New Thread -1238860880 (LWP 10686)] (no debugging symbols found) 0xb7f4a410 in ?? ()
+ Trace 102307
------- Bug created by bug-buddy at 2007-01-15 07:54 ------- Unknown version 2.6.3 in product Evolution. Setting version to "2.6.x".
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!
Hi, I will install the debian package evolution-dbg and try to use it. I will be back in a few days with some more infos.
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!