GNOME Bugzilla – Bug 365677
crash in Evolution: Opening in-line multiple...
Last modified: 2006-10-27 19:23:53 UTC
What were you doing when the application crashed? Opening in-line multiple jpg images in attachment. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 353050624 vsize: 0 resident: 353050624 share: 0 rss: 77320192 rss_rlim: 0 CPU usage: start_time: 1161887968 rtime: 0 utime: 5180 stime: 0 cutime:4822 cstime: 0 timeout: 358 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 -1232611664 (LWP 31865)] [New Thread -1429742688 (LWP 14701)] [New Thread -1376130144 (LWP 14593)] [New Thread -1446528096 (LWP 14591)] [New Thread -1438135392 (LWP 14590)] [New Thread -1363502176 (LWP 31887)] [New Thread -1309140064 (LWP 31883)] [New Thread -1300747360 (LWP 31881)] [New Thread -1292342368 (LWP 31880)] [New Thread -1283196000 (LWP 31879)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 78759
I had this problem also in Ubuntu Dapper with evolution 2.6. Everytime I receive emails with multiple images, if I open them inline by clicking on the drop-down button, after opening 3 or 4 images evolution crashes.
Maurizio, 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! [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 *** This bug has been marked as a duplicate of 333864 ***