GNOME Bugzilla – Bug 360122
crash in Evolution: clicked thash then inbox...
Last modified: 2006-10-27 23:43:23 UTC
What were you doing when the application crashed? clicked thash then inbox in evolution Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 105586688 vsize: 0 resident: 105586688 share: 0 rss: 27942912 rss_rlim: 0 CPU usage: start_time: 1160131648 rtime: 0 utime: 455 stime: 0 cutime:429 cstime: 0 timeout: 26 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 -1233217872 (LWP 5088)] [New Thread -1250591840 (LWP 5181)] [New Thread -1289184352 (LWP 5178)] [New Thread -1297577056 (LWP 5173)] [New Thread -1258984544 (LWP 5124)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 74876
Hi kissro, unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue. For some yet unknown reason, such stacktraces are pretty common currently on certain distros. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue. Just in case you ever can reproduce this crash later, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace. Thanks! Also, please feel free to report any further bugs you find. Thanks! [1] debugging packages for evolution and evolution-data-server, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
description sounds like a duplicate of bug 360237 - please update to evolution 2.8.1.1 and reopen this bug report if this issue still exists. thanks. *** This bug has been marked as a duplicate of 360237 ***