Description of problem: Hmm. Even bug reporting components are crashing now. Yet other software components seem very stable. This was a very clean Fedora 20 install, after abut 10 years of Fedora upgrades (I can't remember exactly, I think the system started with RHL9, maybe?) System mem is at 2.5 GB, Dual Athlon MP 2.8 GHz, AMD chipset. 32-bit. I can induce a hard lock on this system by taking the system mem above 2.5 GB. This is being caused by the mem on the upgraded video card. When the system MB was designed (about 2002), installing a video card with 512 MB video mem was not contemplated therefore not supported by the hardware. I think abrt was attempting to d/l and install debuginfo files for Seamonkey when this crash occurred. Version-Release number of selected component: libreport-gtk-2.2.2-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: report-gtk -- /var/tmp/abrt/ccpp-2014-05-06-22:31:12-19866 crash_function: gtk_symbolic_color_new_mix executable: /usr/bin/report-gtk kernel: 3.13.9-200.fc20.i686 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_symbolic_color_new_mix at deprecated/gtksymboliccolor.c:189 #1 _gtk_gradient_transition at deprecated/gtkgradient.c:543 #2 gtk_css_image_gradient_transition at gtkcssimagegradient.c:174 #3 _gtk_css_image_transition at gtkcssimage.c:199 #4 gtk_css_value_image_transition at gtkcssimagevalue.c:78 #5 _gtk_css_value_transition at gtkcssvalue.c:152 #6 gtk_css_value_array_transition_extend at gtkcssarrayvalue.c:178 #7 _gtk_css_value_transition at gtkcssvalue.c:152 #8 _gtk_css_keyframes_get_value at gtkcsskeyframes.c:529 #9 gtk_css_animation_set_values at gtkcssanimation.c:128
Created attachment 893088 [details] File: backtrace
Created attachment 893089 [details] File: bert_lspci-vvv.txt
Created attachment 893090 [details] File: cgroup
Created attachment 893091 [details] File: core_backtrace
Created attachment 893092 [details] File: dso_list
Created attachment 893093 [details] File: environ
Created attachment 893094 [details] File: exploitable
Created attachment 893095 [details] File: limits
Created attachment 893096 [details] File: maps
Created attachment 893097 [details] File: open_fds
Created attachment 893098 [details] File: proc_pid_status
Created attachment 893099 [details] File: var_log_messages
Thank you for taking the time to report this crash. The attached backtrace is pretty similar [1] to evolution's crash [2]. Based on this evidence, I am switching component from libreport to gtk3. 1: https://retrace.fedoraproject.org/faf/reports/diff/134307/427622/ 2: https://retrace.fedoraproject.org/faf/reports/134307/
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.