GNOME Bugzilla – Bug 405921
crash in Evolution: starting a new message
Last modified: 2007-03-12 12:29:52 UTC
What were you doing when the application crashed? starting a new message Distribution: openSUSE 10.2 (i586) Gnome Release: 2.16.1 2006-11-28 (SUSE) BugBuddy Version: 2.16.0 Memory status: size: 334176256 vsize: 0 resident: 334176256 share: 0 rss: 36126720 rss_rlim: 0 CPU usage: start_time: 1170965713 rtime: 0 utime: 7809 stime: 0 cutime:7352 cstime: 0 timeout: 457 it_real_value: 0 frequency: 0 Backtrace was generated from '/opt/gnome/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1234676032 (LWP 8388)] [New Thread -1405301872 (LWP 8441)] [New Thread -1396909168 (LWP 8439)] [New Thread -1387267184 (LWP 8438)] [New Thread -1377743984 (LWP 8437)] [New Thread -1368958064 (LWP 8425)] [New Thread -1360565360 (LWP 8424)] [New Thread -1352172656 (LWP 8400)] [New Thread -1308894320 (LWP 8399)] [New Thread -1300501616 (LWP 8397)] [New Thread -1291715696 (LWP 8396)] [New Thread -1283322992 (LWP 8394)] [New Thread -1273111664 (LWP 8393)] (no debugging symbols found) 0xb7f83410 in ?? ()
+ Trace 109156
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. Could you please install some debugging packages [1], start the application as normal, 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 in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
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 distributions. 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.