GNOME Bugzilla – Bug 372541
crash in Evolution: Viewing PNG images attac...
Last modified: 2006-11-08 21:14:52 UTC
What were you doing when the application crashed? Viewing PNG images attached to email. May have clicked the drop down too many times since I wanted to view inline but the drop down was at the bottom of the email and I didn't notice it expand down. Maybe some auto-scrolling would help? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 157552640 vsize: 0 resident: 157552640 share: 0 rss: 51466240 rss_rlim: 0 CPU usage: start_time: 1163002246 rtime: 0 utime: 1430 stime: 0 cutime:1327 cstime: 0 timeout: 103 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 -1232595280 (LWP 4215)] [New Thread -1258943584 (LWP 4247)] [New Thread -1314346080 (LWP 4233)] [New Thread -1305953376 (LWP 4232)] [New Thread -1297560672 (LWP 4229)] [New Thread -1276503136 (LWP 4228)] [New Thread -1268110432 (LWP 4225)] [New Thread -1267844192 (LWP 4224)] [New Thread -1250514016 (LWP 4222)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 84413
Chris, 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 ***