GNOME Bugzilla – Bug 366171
crash in Evolution: opening multible images ...
Last modified: 2006-10-28 16:40:45 UTC
What were you doing when the application crashed? opening multible images in evolution email viewer Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 323837952 vsize: 0 resident: 323837952 share: 0 rss: 45756416 rss_rlim: 0 CPU usage: start_time: 1161974128 rtime: 0 utime: 19307 stime: 0 cutime:17849 cstime: 0 timeout: 1458 it_real_value: 0 frequency: 49319 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 -1232865616 (LWP 5822)] [New Thread -1495131232 (LWP 6113)] [New Thread -1478345824 (LWP 6066)] [New Thread -1304077408 (LWP 5934)] [New Thread -1329378400 (LWP 5864)] [New Thread -1337771104 (LWP 5850)] [New Thread -1295684704 (LWP 5840)] [New Thread -1355813984 (LWP 5838)] [New Thread -1347421280 (LWP 5835)] [New Thread -1320866912 (LWP 5832)] [New Thread -1312474208 (LWP 5831)] [New Thread -1287292000 (LWP 5828)] [New Thread -1278899296 (LWP 5827)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 79177
Andreas, 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 ***
*** Bug 366173 has been marked as a duplicate of this bug. ***