GNOME Bugzilla – Bug 372666
crash in Evolution: I was reading an e-mail ...
Last modified: 2006-11-08 21:42:40 UTC
What were you doing when the application crashed? I was reading an e-mail with images attached. Evolution hanged up when I clicked on the icon to see the picture. I had the same problem sometimes with the previous version shipped with Ubuntu. I can't reproduce the error, but it will happen if I open enough images attached to emails. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 258670592 vsize: 0 resident: 258670592 share: 0 rss: 46620672 rss_rlim: 0 CPU usage: start_time: 1163015875 rtime: 0 utime: 3669 stime: 0 cutime:3260 cstime: 0 timeout: 409 it_real_value: 0 frequency: 10 Backtrace was generated from '/usr/bin/evolution-2.8' (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 -1233324368 (LWP 5577)] [New Thread -1382339680 (LWP 19177)] [New Thread -1309975648 (LWP 5725)] [New Thread -1372632160 (LWP 5723)] [New Thread -1318368352 (LWP 5719)] [New Thread -1326797920 (LWP 5699)] [New Thread -1293190240 (LWP 5687)] [New Thread -1284797536 (LWP 5686)] [New Thread -1276404832 (LWP 5685)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 84511
Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue. However, according to the description this is the same issue as bug 333864, which is fixed in Evolution 2.8.1.1. Just in case you can reproduce this crash later, please consider installing debugging packages [1], which help a lot in tracking down the crash. Thanks! Also, please feel free to report any further bugs you find. Thanks! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions *** This bug has been marked as a duplicate of 333864 ***