Version-Release number of selected component: evolution-3.8.5-2.fc19 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/evolution crash_function: type_check_is_value_type_U executable: /usr/bin/evolution kernel: 3.13.5-103.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 type_check_is_value_type_U at gtype.c:4131 #1 g_type_check_value at gtype.c:4173 #2 g_value_unset at gvalue.c:269 #3 g_object_new_valist at gobject.c:1839 #5 g_object_bind_property_full at gbinding.c:936 #6 g_object_bind_property at gbinding.c:1010 #7 settings_mail_formatter_constructed at e-settings-mail-formatter.c:143 #9 g_object_new_valist at gobject.c:1836 #11 extensible_load_extension at e-extensible.c:97 #12 e_type_traverse at e-module.c:362 Potential duplicate: bug 714813
Created attachment 872228 [details] File: backtrace
Created attachment 872229 [details] File: cgroup
Created attachment 872230 [details] File: core_backtrace
Created attachment 872231 [details] File: dso_list
Created attachment 872232 [details] File: environ
Created attachment 872233 [details] File: exploitable
Created attachment 872234 [details] File: limits
Created attachment 872235 [details] File: maps
Created attachment 872236 [details] File: open_fds
Created attachment 872237 [details] File: proc_pid_status
Created attachment 872238 [details] File: var_log_messages
Thanks for a bug report. This looks like a memory corruption bug (like when some code wrote to an already freed memory or any such issue), but I cannot tell for sure without being able to reproduce this. Maybe this will partly addressed with a fix for an upstream bug report [1], which landed for 3.12.0, but I'm not certain of it, because another upstream bug [2] can have its influence on this as well. Do you see this crash often? Does it do only a certain message? A workaround would be to disable automatic image loading (Edit->Preferences->Mail Preferences->HTML Messages tab), but that may not always work too. [1] https://bugzilla.gnome.org/show_bug.cgi?id=725402 [2] https://bugzilla.gnome.org/show_bug.cgi?id=720740
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.