GNOME Bugzilla – Bug 400689
crash in Evolution: Estaba abriendo una imag...
Last modified: 2009-12-28 01:43:40 UTC
What were you doing when the application crashed? Estaba abriendo una imagen que he recibido adjunta a un correo Distribution: Gentoo Base System version 1.12.6 Gnome Release: 2.16.2 2006-12-29 (Gentoo) BugBuddy Version: 2.16.0 Memory status: size: 110776320 vsize: 0 resident: 110776320 share: 0 rss: 32129024 rss_rlim: 0 CPU usage: start_time: 1169746814 rtime: 0 utime: 769 stime: 0 cutime:677 cstime: 0 timeout: 92 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/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231645008 (LWP 5324)] [New Thread -1295303776 (LWP 5340)] [New Thread -1294693472 (LWP 5339)] [New Thread -1257038944 (LWP 5338)] [New Thread -1266680928 (LWP 5337)] [New Thread -1275466848 (LWP 5333)] [New Thread -1248609376 (LWP 5330)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 105198
Thread 1 (Thread -1231645008 (LWP 5324))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 401126 has been marked as a duplicate of this bug. ***
*** Bug 431194 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
*** Bug 474858 has been marked as a duplicate of this bug. ***
from bug 451408:
+ Trace 182304
*** Bug 451408 has been marked as a duplicate of this bug. ***
*** Bug 490736 has been marked as a duplicate of this bug. ***
I would like to see the attachment header or the mail itself which causes it. It's relatively easy to prevent crash, but it's kind of workaround, so it would be better to see what kind of message causes it. Can someone of you attach here such message, or copy the beginning of image part from message source? (Ctrl+U is for message source). Thanks in advance.
*** Bug 505751 has been marked as a duplicate of this bug. ***
*** Bug 509484 has been marked as a duplicate of this bug. ***
NEEDINFO as per comment 9. Please provide the requested information.