Version-Release number of selected component: evolution-3.10.1-1.fc20 Additional info: reporter: libreport-2.1.8 backtrace_rating: 4 cmdline: evolution crash_function: magazine_cache_pop_magazine executable: /usr/bin/evolution kernel: 3.11.6-300.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_cache_pop_magazine at gslice.c:739 #1 thread_memory_magazine1_reload at gslice.c:807 #2 g_slice_alloc at gslice.c:1005 #3 pango_layout_line_new at pango-layout.c:4777 #4 process_line at pango-layout.c:3621 #5 pango_layout_check_lines at pango-layout.c:3979 #6 pango_layout_get_extents_internal at pango-layout.c:2539 #7 pango_layout_get_extents at pango-layout.c:2734 #8 gtk_label_get_preferred_layout_size at gtklabel.c:3584 #9 gtk_label_get_preferred_size at gtklabel.c:3641
Created attachment 815394 [details] File: backtrace
Created attachment 815395 [details] File: cgroup
Created attachment 815396 [details] File: core_backtrace
Created attachment 815397 [details] File: dso_list
Created attachment 815398 [details] File: environ
Created attachment 815399 [details] File: exploitable
Created attachment 815400 [details] File: limits
Created attachment 815402 [details] File: maps
Created attachment 815403 [details] File: open_fds
Created attachment 815404 [details] File: proc_pid_status
Thanks for a bug report. There seemed to happen some (software) memory corruption, probably caused by a code which wrote to a memory which was not supposed to be written to, like writing to a memory which was released by other part of the code (which can be also caused by a reference counting errors). Such issues can be "found" on any places, it depends what was written in that overwritten part of memory and when it is accessed (the 'found' is like 'application crashes' or some basic memory checking fails). That said, it highly depends what was done before the crash. By any chance, did you get any similar crashes after certain steps, please?
*** Bug 1022987 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.