GNOME Bugzilla – Bug 366563
crash in Evolution: I opened an email that i...
Last modified: 2006-10-30 11:48:36 UTC
What were you doing when the application crashed? I opened an email that includes an attachment. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 104435712 vsize: 0 resident: 104435712 share: 0 rss: 30199808 rss_rlim: 0 CPU usage: start_time: 1162078481 rtime: 0 utime: 489 stime: 0 cutime:460 cstime: 0 timeout: 29 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 -1232890192 (LWP 4674)] [New Thread -1291424864 (LWP 4692)] [New Thread -1282937952 (LWP 4690)] [New Thread -1273144416 (LWP 4689)] [New Thread -1264751712 (LWP 4685)] [New Thread -1256322144 (LWP 4681)] [New Thread -1247929440 (LWP 4680)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 79502
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
Hi, thanks for the prompt reply. I installed the debugging packages as you said and tried to reproduce the bug. I should note that the bug was produced the first time I opened this version of Evolution (after upgrading). The first time that this happened I: - logged into Gnome. - opened Evolution. - clicked on a new email (that incidentally had image file attachments). After restarting Evolution, the email could be read without a problem. So to reproduce this I: - Marked the email that first produced the bug as Read. - Clicked another email to remove focus from the "bug-producing" email. - Closed Evolution. - Logged out of Gnome and logged back in again (this step was necessary to reproduce the bug). - Opened Evolution. - Clicked on the email that originally produced the bug. Please do tell me if you need any other information. I am more than willing to help. Thanks again. Below is the copy-pasted Details section of bug-buddy. I hope it is helpful. ---------------------------------------------------------------- Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 103231488 vsize: 0 resident: 103231488 share: 0 rss: 29904896 rss_rlim: 0 CPU usage: start_time: 1162089888 rtime: 0 utime: 516 stime: 0 cutime:496 cstime: 0 timeout: 20 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 -1232959824 (LWP 4592)] [New Thread -1283384416 (LWP 4608)] [New Thread -1273205856 (LWP 4607)] [New Thread -1264813152 (LWP 4603)] [New Thread -1256383584 (LWP 4599)] [New Thread -1247990880 (LWP 4598)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 79554
Thread 1 (Thread -1232959824 (LWP 4592))
Thanks, nice trace. This is the same issue as bug 333864, which is fixed in Evolution 2.8.1.1. *** This bug has been marked as a duplicate of 333864 ***