GNOME Bugzilla – Bug 412250
crash in Evolution: viewing inline photos
Last modified: 2007-04-13 19:57:59 UTC
What were you doing when the application crashed? viewing inline photos Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 166694912 vsize: 0 resident: 166694912 share: 0 rss: 57217024 rss_rlim: 0 CPU usage: start_time: 1172499610 rtime: 0 utime: 1594 stime: 0 cutime:1521 cstime: 0 timeout: 73 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 -1233381712 (LWP 9255)] [New Thread -1315873888 (LWP 9283)] [New Thread -1302332512 (LWP 9274)] [New Thread -1281553504 (LWP 9273)] [New Thread -1299727456 (LWP 9270)] [New Thread -1273160800 (LWP 9269)] [New Thread -1264768096 (LWP 9265)] [New Thread -1256338528 (LWP 9261)] [New Thread -1247945824 (LWP 9260)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 114024
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
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Created attachment 85964 [details] new stacktrace with debugging pkg for bug id 412250
Hi Jonathan, Thanks for your feedback. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 351374 ***