GNOME Bugzilla – Bug 396877
crash in Evolution: Showing an attached phot...
Last modified: 2007-02-23 09:03:28 UTC
What were you doing when the application crashed? Showing an attached photo inline Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 293396480 vsize: 0 resident: 293396480 share: 0 rss: 120401920 rss_rlim: 0 CPU usage: start_time: 1168869284 rtime: 0 utime: 4091 stime: 0 cutime:3943 cstime: 0 timeout: 148 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 -1232894288 (LWP 7212)] [New Thread -1351808096 (LWP 7238)] [New Thread -1343415392 (LWP 7237)] [New Thread -1334314080 (LWP 7223)] [New Thread -1325528160 (LWP 7222)] [New Thread -1277236320 (LWP 7220)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 102386
Thread 6 (Thread -1277236320 (LWP 7220))
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 ***