GNOME Bugzilla – Bug 371335
crash in Evolution: Este problema acontece c...
Last modified: 2006-11-07 00:25:06 UTC
What were you doing when the application crashed? Este problema acontece comigo desde a versão 6.06 do Ubuntu. Quando abro muitas imagens anexas embutidas no painel de mensagens do Evolution, ele tende a travar. This problem happens to me since Ubuntu's version 6.06. Whenever I open too much attached imagens embedded in Evolution's message pane, it tends to crash. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 150384640 vsize: 0 resident: 150384640 share: 0 rss: 27373568 rss_rlim: 0 CPU usage: start_time: 1162764230 rtime: 0 utime: 2104 stime: 0 cutime:1952 cstime: 0 timeout: 152 it_real_value: 0 frequency: 668 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 -1232767312 (LWP 4946)] [New Thread -1261237344 (LWP 9465)] [New Thread -1318233184 (LWP 6587)] [New Thread -1309447264 (LWP 4966)] [New Thread -1301054560 (LWP 4965)] [New Thread -1292661856 (LWP 4964)] [New Thread -1270101088 (LWP 4956)] [New Thread -1252844640 (LWP 4953)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 83457
Gláuber, 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 ***