GNOME Bugzilla – Bug 367560
crash in Evolution: trying to start a new ma...
Last modified: 2006-11-08 17:41:33 UTC
What were you doing when the application crashed? trying to start a new mail Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 167268352 vsize: 0 resident: 167268352 share: 0 rss: 36737024 rss_rlim: 0 CPU usage: start_time: 1162207556 rtime: 0 utime: 1383 stime: 0 cutime:1178 cstime: 0 timeout: 205 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
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
Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 166789120 vsize: 0 resident: 166789120 share: 0 rss: 36950016 rss_rlim: 0 CPU usage: start_time: 1162222095 rtime: 0 utime: 846 stime: 0 cutime:780 cstime: 0 timeout: 66 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1233193296 (LWP 16488)] [New Thread -1358472288 (LWP 16525)] [New Thread -1350079584 (LWP 16523)] [New Thread -1341686880 (LWP 16522)] [New Thread -1333294176 (LWP 16521)] [New Thread -1324901472 (LWP 16515)] [New Thread -1316508768 (LWP 16514)] [New Thread -1295402080 (LWP 16513)] [New Thread -1287009376 (LWP 16512)] [New Thread -1278223456 (LWP 16511)] [New Thread -1261438048 (LWP 16510)] [New Thread -1269830752 (LWP 16495)] [New Thread -1250604128 (LWP 16493)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 80484
Thread 1 (Thread -1233193296 (LWP 16488))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. This issue has been fixed in vesion 2.8.1.1. *** This bug has been marked as a duplicate of 360237 ***