GNOME Bugzilla – Bug 369902
crash in Evolution: Viewing an image inline ...
Last modified: 2006-11-03 21:08:45 UTC
What were you doing when the application crashed? Viewing an image inline Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 280760320 vsize: 0 resident: 280760320 share: 0 rss: 53686272 rss_rlim: 0 CPU usage: start_time: 1162484793 rtime: 0 utime: 2727 stime: 0 cutime:2572 cstime: 0 timeout: 155 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/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232587088 (LWP 5519)] [New Thread -1410880608 (LWP 5734)] [New Thread -1392624736 (LWP 5582)] [New Thread -1384223840 (LWP 5578)] [New Thread -1375831136 (LWP 5577)] [New Thread -1367438432 (LWP 5571)] [New Thread -1358652512 (LWP 5540)] [New Thread -1350259808 (LWP 5539)] [New Thread -1341867104 (LWP 5536)] [New Thread -1294492768 (LWP 5534)] [New Thread -1285706848 (LWP 5533)] [New Thread -1276150880 (LWP 5531)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 82270
Kevin, 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 ***