GNOME Bugzilla – Bug 367288
crash in Evolution: Opening a jpeg attachmen...
Last modified: 2006-11-02 00:59:49 UTC
What were you doing when the application crashed? Opening a jpeg attachment from my mail. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 173498368 vsize: 0 resident: 173498368 share: 0 rss: 60862464 rss_rlim: 0 CPU usage: start_time: 1162167960 rtime: 0 utime: 730 stime: 0 cutime:658 cstime: 0 timeout: 72 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 -1232648528 (LWP 10036)] [New Thread -1320838240 (LWP 10047)] [New Thread -1312445536 (LWP 10046)] [New Thread -1270305888 (LWP 10042)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 80126
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. However, according to the description this is the same issue as bug 333864, which is fixed in Evolution 2.8.1.1. Just in case you can reproduce this crash later, please consider installing debugging packages [1], which help a lot in tracking down the crash. Thanks! Also, please feel free to report any further bugs you find. Thanks! *** This bug has been marked as a duplicate of 333864 ***