GNOME Bugzilla – Bug 419186
crash in em-format-html-display.c:1782
Last modified: 2008-05-22 08:00:00 UTC
What were you doing when the application crashed? Distribution: Gentoo Base System release 1.12.9 Gnome Release: 2.16.2 2007-02-09 (Gentoo) BugBuddy Version: 2.16.0 Memory status: size: 148787200 vsize: 0 resident: 148787200 share: 0 rss: 23859200 rss_rlim: 0 CPU usage: start_time: 1174093541 rtime: 0 utime: 130 stime: 0 cutime:120 cstime: 0 timeout: 10 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 -1232152912 (LWP 7133)] [New Thread -1351468128 (LWP 7196)] [New Thread -1297564768 (LWP 7195)] [New Thread -1322742880 (LWP 7194)] [New Thread -1314350176 (LWP 7191)] [New Thread -1305957472 (LWP 7190)] [New Thread -1288778848 (LWP 7189)] [New Thread -1280386144 (LWP 7181)] [New Thread -1271993440 (LWP 7180)] [New Thread -1263432800 (LWP 7179)] [New Thread -1255040096 (LWP 7178)] [New Thread -1246520416 (LWP 7177)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 119290
Thread 1 (Thread -1232152912 (LWP 7133))
*** Bug 419269 has been marked as a duplicate of this bug. ***
*** Bug 460670 has been marked as a duplicate of this bug. ***
*** Bug 460307 has been marked as a duplicate of this bug. ***
bug 460307: evolution-mail-ERROR **: file em-format-html-display.c: line 1782 (efhd_attachment_button): assertion failed: (info != NULL)
The code there has been changed, and it will not crash anymore, it will write a warning message on the console "unable to expand the attachment" and no picture will be shown. Is it possible if anyone of you can attach here a message which caused the error? (If it doesn't contain any confidential/private data.) Also, was it a regular email or a junk/spam? Thanks in advance.
*** Bug 481111 has been marked as a duplicate of this bug. ***
*** Bug 473313 has been marked as a duplicate of this bug. ***
*** Bug 494717 has been marked as a duplicate of this bug. ***
Closing as per comment#5 if you still see this issue with a current release of evolution (2.22.x or later), please reopen. thanks in advance.