GNOME Bugzilla – Bug 362039
crash in Evolution: Quitting Evolution
Last modified: 2006-10-20 17:51:42 UTC
What were you doing when the application crashed? Quitting Evolution Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 156180480 vsize: 0 resident: 156180480 share: 0 rss: 29261824 rss_rlim: 0 CPU usage: start_time: 1160777310 rtime: 0 utime: 366 stime: 0 cutime:336 cstime: 0 timeout: 30 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 -1233008976 (LWP 7000)] [New Thread -1345520736 (LWP 7037)] [New Thread -1337128032 (LWP 7028)] [New Thread -1292358752 (LWP 7014)] [New Thread -1283568736 (LWP 7011)] [New Thread -1275044960 (LWP 7009)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 76213
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. 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
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! Closing this bug report as no further information has been provided. Also, please feel free to report any further bugs you find. Thanks!
Yep, sorry for not coming back with more information. I immediately installed the relevant packages for debugging but after an Ubuntu upgrade (I'm following Edgy at the moment) the problem seemed to vanish and I've been unable to reproduce it again. I guess it must already have been fixed - thanks!
Ah, nice -- thanks for the feedback. :) That would be the same issue as bug 334966. This fix has been backported to Ubuntu packages recently. According to the description and considering the crash does not occur for you since updating, this most likely is the bug you encountered. Marking as such...
*** This bug has been marked as a duplicate of 334966 ***
Thanks for caring, much appreciated! :)