GNOME Bugzilla – Bug 484212
crash in Evolution: I have an Email with 5 J...
Last modified: 2007-10-19 00:57:17 UTC
What were you doing when the application crashed? I have an Email with 5 Jpgs attached open (all 5 jpegs are open) and am saving the jpegs to a folder on the HD. After opening the Email, I saved the first jpeg and closed the image by clicking the little arrow above it. I used the little save menu on the second jpeg image to save it and the crash occurred when I clicked the little orange arrow to close the jpeg image in the message. The first jpeg is 987 KB in size, the second one is 594 KB. The Eye of Gnome viewer shows both images as OK, that is, not corrupt. **** I just went to another desktop, reloaded Evolution and re-opened the Email with the 5 jpegs in it. I saved the remaining three jpeg files with no problems but I did not try to close the image after saving. The size of the remaining files are about 1 MB each. As before, Eye of Gnome continues to show no corruption in the images. After re-reading this report, I decided to run another test, that is, I opened the Evolution Email with 5 jpegs attached and then moved to the first jpeg and clicked the little orange arrow to tell it to close. The application crashed. I closed that Bug report since I figure we have it covered here. I will retry the error if you send me a request. I reported a similar bug in June number 443066. I dunno if its still there but here is a link to it: http://bugzilla.gnome.org/show_bug.cgi?id=443066 That is about all I got on this one. Don Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 210067456 vsize: 0 resident: 210067456 share: 0 rss: 84557824 rss_rlim: 0 CPU usage: start_time: 1191693662 rtime: 0 utime: 3328 stime: 0 cutime:3121 cstime: 0 timeout: 207 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232484688 (LWP 9934)] [New Thread -1318114400 (LWP 9960)] [New Thread -1309721696 (LWP 9958)] [New Thread -1261438048 (LWP 9950)] [New Thread -1278223456 (LWP 9949)] [New Thread -1286616160 (LWP 9942)] [New Thread -1269830752 (LWP 9939)] [New Thread -1251202144 (LWP 9937)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 168379
Thread 1 (Thread -1232484688 (LWP 9934))
Thanks for taking the time to report this bug. 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 340165 ***