GNOME Bugzilla – Bug 362040
crash in Evolution: Evolution crashed after ...
Last modified: 2006-10-17 01:35:42 UTC
What were you doing when the application crashed? Evolution crashed after I clicked on an email (on the list of emails), while it was receiving new emails. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 208543744 vsize: 0 resident: 208543744 share: 0 rss: 45297664 rss_rlim: 0 CPU usage: start_time: 1160651017 rtime: 0 utime: 21028 stime: 0 cutime:19216 cstime: 0 timeout: 1812 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 -1233226064 (LWP 5185)] [New Thread -1292592224 (LWP 21872)] [New Thread -1338393696 (LWP 5561)] [New Thread -1275401312 (LWP 5560)] [New Thread -1327158368 (LWP 5269)] [New Thread -1309377632 (LWP 5202)] [New Thread -1300984928 (LWP 5201)] [New Thread -1266971744 (LWP 5194)] [New Thread -1258579040 (LWP 5193)] [New Thread -1250186336 (LWP 5192)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 76214
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! Can you reproduce this? [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
I installed all the debug packages, but now I'm unable to reproduce the bug... So, if I manage to reproduce it, I'll attach the trace here.
I'm not sure it's the same bug, but I had another crash today, with hopefully a better trace. It's bug #362753.
*** This bug has been marked as a duplicate of 362753 ***