This is just a quick note about my discovery. I get the following crash in evolution-mail when viewing mails with attachments with certain mime types ( eg. application/vnd.ms-powerpoint ). #7 0x4002f8a0 in read_num_val () from /usr/lib/libgnomevfs.so.0 #8 0x4002e232 in gnome_vfs_mime_magic_parse () from /usr/lib/libgnomevfs.so.0 #9 0x4002e93c in gnome_vfs_mime_get_type_from_magic_table () from /usr/lib/libgnomevfs.so.0 #10 0x40030777 in gnome_vfs_get_mime_type_internal () from /usr/lib/libgnomevfs.so.0 #11 0x4002f163 in gnome_vfs_get_mime_type_for_buffer () from /usr/lib/libgnomevfs.so.0 #12 0x080ada82 in mail_identify_mime_part () #13 0x080ad9fb in mail_identify_mime_part () #14 0x080a7b42 in mail_lookup_handler () #15 0x080ace17 in mail_part_toggle_displayed () #16 0x080a799e in mail_lookup_handler () #17 0x0809f34f in mail_display_render () #18 0x0807a066 in folder_browser_charset_changed () #19 0x080b633f in mail_execute_shell_command () #20 0x080b2859 in mail_async_event_destroy () #21 0x49dd17ac in g_io_unix_dispatch () from /usr/lib/libglib-1.2.so.0 #22 0x49dd3d55 in g_main_dispatch () from /usr/lib/libglib-1.2.so.0 #23 0x49dd3b1b in g_main_iterate () from /usr/lib/libglib-1.2.so.0 #24 0x49dd2b54 in g_main_run () from /usr/lib/libglib-1.2.so.0 #25 0x49efc68f in gtk_main () from /usr/lib/libgtk-1.2.so.0 #26 0x4a627472 in bonobo_main () from /usr/lib/libbonobo.so.2 #27 0x080c26df in main () #28 0x49b03e34 in __libc_start_main () from /lib/libc.so.6 I have traced the crash to line 227 in libgnomevfs/gnome-vfs-mime-magic.c It seems that if you compile gnome-vfs with any CFLAGS instead of "" then it crashes with the above backtrace. Even the default ones in gnome-vfs, "-O2 -g", fail!!! This was with using the sys-devel/gcc-3.2.1-r6 - I guess it is at fault! My solution was to use CFLAGS="" emerge gnome-vfs-1.0.5-r2.ebuild This is only for future referance if anyone else comes across it! No action needed. This fixed it.
The issue is already known and Azarah made a patch for it in the 1.0.5-r3, please try that one *** This bug has been marked as a duplicate of 12478 ***