GNOME Bugzilla – Bug 369978
crash in Evolution: I tried to remove a atta...
Last modified: 2006-11-04 04:40:22 UTC
What were you doing when the application crashed? I tried to remove a attachment (a textfile). Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 272670720 vsize: 0 resident: 272670720 share: 0 rss: 62504960 rss_rlim: 0 CPU usage: start_time: 1162541750 rtime: 0 utime: 11215 stime: 0 cutime:10673 cstime: 0 timeout: 542 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 -1233197392 (LWP 5607)] [New Thread -1371042912 (LWP 6234)] [New Thread -1357505632 (LWP 5645)] [New Thread -1349112928 (LWP 5644)] [New Thread -1340720224 (LWP 5641)] [New Thread -1340453984 (LWP 5637)] [New Thread -1331659872 (LWP 5635)] [New Thread -1323267168 (LWP 5634)] [New Thread -1314874464 (LWP 5631)] [New Thread -1288803424 (LWP 5627)] [New Thread -1263195232 (LWP 5626)] [New Thread -1279980640 (LWP 5625)] [New Thread -1271587936 (LWP 5622)] [New Thread -1253725280 (LWP 5620)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 82328
(In reply to comment #0) > I tried to remove a attachment (a textfile). I assume that would be inside the Composer, right? Sander, 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 357492. 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 357492 ***