Description of problem: While trying to install Skype 64 bit and Chrome 64 bit downloads from their homepages with YUM Extender: A kernel problem occurred, but your kernel has been tainted (flags:GW). Kernel maintainers are unable to diagnose tainted reports. I use Fedora 20 Cinnamon. Version-Release number of selected component: gnome-abrt-0.3.5 Additional info: reporter: libreport-2.1.12 kernel: 3.13.3-201.fc20.x86_64 type: libreport
Created attachment 865527 [details] File: Screenshot from 2014-02-20 14:42:33.png
Thank you for the report. Unfortunately, this is the correct behaviour. Visit the followin URL for more details: http://abrt.readthedocs.org/en/latest/faq.html#what-is-tainted-kernel-and-why-is-my-kernel-tainted Was that tainted kernel oops the only oops ABRT detected? If so, I think this report is a dupe bug #1045900.
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.
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.
The update did fix the problem. Thank you very much.