GNOME Bugzilla – Bug 390604
crash in Evolution: Trying to open an email ...
Last modified: 2007-02-09 07:42:21 UTC
What were you doing when the application crashed? Trying to open an email with 3MB picture attachments Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 214003712 vsize: 0 resident: 214003712 share: 0 rss: 39251968 rss_rlim: 0 CPU usage: start_time: 1167381790 rtime: 0 utime: 4997 stime: 0 cutime:4685 cstime: 0 timeout: 312 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232574800 (LWP 20108)] [New Thread -1379533904 (LWP 20188)] [New Thread -1371145296 (LWP 20185)] [New Thread -1331414096 (LWP 20166)] [New Thread -1323025488 (LWP 20164)] [New Thread -1276003408 (LWP 20163)] [New Thread -1284392016 (LWP 20144)] [New Thread -1267577936 (LWP 20139)] (no debugging symbols found) 0xb71bee91 in waitpid () from /lib/libc.so.6
+ Trace 97734
Thread 8 (Thread -1267577936 (LWP 20139))
Thread 7 (Thread -1284392016 (LWP 20144))
Thread 6 (Thread -1276003408 (LWP 20163))
Thread 5 (Thread -1323025488 (LWP 20164))
Thread 4 (Thread -1331414096 (LWP 20166))
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 am unable to do this stack trace as I never had the debugging tools installed and now can't reproduce the problem. I have the debugging tools installed and if it happens again I'll post a new bug. Sorry about that. Justin
Ok, I'm closing for now as INCOMPLETE then. If you manage to reproduce the problem, then please re-open this bug.
Likely a duplicate of bug 340165 or 333864. Fixed in 2.8.3 and 2.9.x
*** This bug has been marked as a duplicate of 340165 ***