GNOME Bugzilla – Bug 353382
crash in Evolution: Deleting an attachment.....
Last modified: 2006-11-17 23:28:23 UTC
What were you doing when the application crashed? Deleting an attachment... Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.92 2006-08-22 (Ubuntu) BugBuddy Version: 2.15.92 Memory status: size: 310808576 vsize: 0 resident: 310808576 share: 0 rss: 53014528 rss_rlim: 0 CPU usage: start_time: 1156835493 rtime: 0 utime: 3335 stime: 0 cutime:3129 cstime: 0 timeout: 206 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 -1209174352 (LWP 32686)] [New Thread -1348826208 (LWP 426)] [New Thread -1349342304 (LWP 424)] [New Thread -1339036768 (LWP 32716)] [New Thread -1330644064 (LWP 32715)] [New Thread -1322251360 (LWP 32710)] [New Thread -1281365088 (LWP 32698)] [New Thread -1272972384 (LWP 32696)] [New Thread -1262986336 (LWP 32694)] [New Thread -1254593632 (LWP 32693)] [New Thread -1246200928 (LWP 32692)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 71183
Thread 1 (Thread -1209174352 (LWP 32686))
More concretely, what I did was: 1. open a mail from sent folder with doble click 2. Edit as new message 3. Try to reemplace the attachment with a new versión of the same file.. cheers... Sergi
Thanks for the detailed description, Sergi. :) Although the stacktraces do not match entirely, I believe this to be the same issue as bug 357492. The description is the same, and these are the only crashes in e_attachment_bar_remove_selected() so far, no other duplicates at all. The difference in the stacktraces likely is due to different actions (keyboard shortcut vs. context menu). Marking this bug as duplicate of the later filed one, because the other one got a stacktrace with debugging symbols. Please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 357492 ***
*** Bug 360105 has been marked as a duplicate of this bug. ***
*** Bug 375512 has been marked as a duplicate of this bug. ***