GNOME Bugzilla – Bug 368383
crash in Evolution: I was opening the third ...
Last modified: 2006-10-31 20:25:15 UTC
What were you doing when the application crashed? I was opening the third of several attached jpeg in line images. This has happened in older versions after several images were opened. I suspected a lack of memory at first but perhaps it is a bad jpeg? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 205393920 vsize: 0 resident: 205393920 share: 0 rss: 35794944 rss_rlim: 0 CPU usage: start_time: 1162308491 rtime: 0 utime: 1378 stime: 0 cutime:1281 cstime: 0 timeout: 97 it_real_value: 0 frequency: 8 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 -1232824656 (LWP 4845)] [New Thread -1379423328 (LWP 5143)] [New Thread -1371030624 (LWP 5015)] [New Thread -1370764384 (LWP 5007)] [New Thread -1361863776 (LWP 5000)] [New Thread -1353471072 (LWP 4999)] [New Thread -1300120672 (LWP 4977)] [New Thread -1291322464 (LWP 4976)] [New Thread -1282892896 (LWP 4964)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 81045
Memory constraints seem highly unlikely, a bad jpeg is possible. However, this most likely is a known bug yet again... 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 ***