GNOME Bugzilla – Bug 368240
crash in Evolution: Opening an inline JPG at...
Last modified: 2006-10-31 18:07:46 UTC
What were you doing when the application crashed? Opening an inline JPG attachment. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 699125760 vsize: 0 resident: 699125760 share: 0 rss: 358154240 rss_rlim: 0 CPU usage: start_time: 1162278572 rtime: 0 utime: 13907 stime: 0 cutime:11708 cstime: 0 timeout: 2199 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 3496)] [New Thread -1410958432 (LWP 4604)] [New Thread -1385514080 (LWP 3787)] [New Thread -1347429472 (LWP 3523)] [New Thread -1339036768 (LWP 3522)] [New Thread -1330644064 (LWP 3519)] [New Thread -1298416736 (LWP 3517)] [New Thread -1281631328 (LWP 3514)] [New Thread -1290024032 (LWP 3511)] [New Thread -1273197664 (LWP 3507)] [New Thread -1264804960 (LWP 3506)] [New Thread -1256375392 (LWP 3505)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 80923
Edward, 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 ***