GNOME Bugzilla – Bug 414544
Sudden crash after deleting an e-mail
Last modified: 2007-03-04 15:37:56 UTC
Distribution: Debian 4.0 Package: Evolution Severity: Normal Version: GNOME2.14.3 2.6.3 Gnome-Distributor: Debian Synopsis: Sudden crash after deleting an e-mail Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Bugzilla-Version: 2.6.3 BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: I deleted an e-mail containing a medium-sized JPG (about 300K), then deleted a Spam e-mail, and as it automatically moved to the next e-mail it suddenly crashed. Steps to reproduce the crash: 1. This was unexpected, I haven't seen this before. 2. 3. Expected Results: How often does this happen? First time Additional Information: My machine is a low-power 1GHz VIA C3 "Hush PC" using ReiserFS for its filesystems and fvwm-Crystal as its desktop. It is typically left on permanently and the only other (unrelated) error I have encountered is occasionally (every 2 or 3 weeks) the mouse pointer will disappear and I usually end up having to Ctrl-Alt-Backspace to kill and restart the X-Server. Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.6' (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 -1231620416 (LWP 3116)] [New Thread -1284506704 (LWP 6185)] [New Thread -1293829200 (LWP 3148)] [New Thread -1276118096 (LWP 3146)] [New Thread -1267729488 (LWP 3145)] [New Thread -1257415760 (LWP 3143)] [New Thread -1247196240 (LWP 3125)] [New Thread -1237668944 (LWP 3124)] (no debugging symbols found) 0xb7738231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 115715
Thread 1 (Thread -1231620416 (LWP 3116))
------- Bug created by bug-buddy at 2007-03-04 11:57 ------- Unknown version 2.6.3 in product Evolution. Setting version to "2.6.x".
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 350981 ***