GNOME Bugzilla – Bug 363626
crash in Evolution: Pressing the send / rece...
Last modified: 2007-09-26 18:00:07 UTC
What were you doing when the application crashed? Pressing the send / receive toolbar button right after starting it. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 183115776 vsize: 0 resident: 183115776 share: 0 rss: 42029056 rss_rlim: 0 CPU usage: start_time: 1161339964 rtime: 0 utime: 285 stime: 0 cutime:269 cstime: 0 timeout: 16 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 -1232447824 (LWP 5759)] [New Thread -1350567008 (LWP 5774)] [New Thread -1340707936 (LWP 5773)] [New Thread -1288979552 (LWP 5769)] [New Thread -1279919200 (LWP 5768)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 77290
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!
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 364700 ***