GNOME Bugzilla – Bug 386171
crash in Evolution: Abriendo un fichero adju...
Last modified: 2007-02-23 09:01:36 UTC
What were you doing when the application crashed? Abriendo un fichero adjunto(extensión .jpg) a un mensaje de correo electrónico. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 188751872 vsize: 0 resident: 188751872 share: 0 rss: 43757568 rss_rlim: 0 CPU usage: start_time: 1166183931 rtime: 0 utime: 5776 stime: 0 cutime:5129 cstime: 0 timeout: 647 it_real_value: 0 frequency: 2946 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 -1232759120 (LWP 21393)] [New Thread -1356112992 (LWP 21775)] [New Thread -1350788192 (LWP 21456)] [New Thread -1342375008 (LWP 21455)] [New Thread -1333281888 (LWP 21402)] [New Thread -1324889184 (LWP 21401)] [New Thread -1277060192 (LWP 21397)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 94372
Thread 7 (Thread -1277060192 (LWP 21397))
Thread 2 (Thread -1356112992 (LWP 21775))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
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. Note, that this does not happen always, but sporadically only. 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!
*** This bug has been marked as a duplicate of 333864 ***