GNOME Bugzilla – Bug 388097
crash in Evolution: Fucking getting pissed a...
Last modified: 2007-02-23 09:02:59 UTC
What were you doing when the application crashed? Fucking getting pissed at the program. It wont let me open a picture in evolution. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 231124992 vsize: 0 resident: 231124992 share: 0 rss: 117071872 rss_rlim: 0 CPU usage: start_time: 1166656104 rtime: 0 utime: 1696 stime: 0 cutime:1639 cstime: 0 timeout: 57 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 -1233443152 (LWP 5481)] [New Thread -1275769952 (LWP 5490)] [New Thread -1284162656 (LWP 5489)] [New Thread -1293026400 (LWP 5487)] [New Thread -1267340384 (LWP 5484)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 95824
Thread 5 (Thread -1267340384 (LWP 5484))
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! Also, does this happen for all images? What are your build flags for gentoo?
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. Please ask your distributor for updates. 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 ***