Red Hat Bugzilla – Bug 805337
abrt continues to file tainted bugs
Last modified: 2015-01-04 17:31:50 EST
look at bug 805218 (and all the dupes filed against it). None of those traces are interesting, because they are Tainted: W, meaning something bad already happened, so this is likely all fallout from the first problem. (abrt didn't actually file the untainted trace for some reason afaict).
yea I know and all it's because the new abrt is not yet in fedora; patches are still in git only.
ah, I thought those changes made it into 2.0.7 Any idea how long before we see the newer abrt rolled out for f16 users ?
soon, I hope this week. we have to add one feature to abrt and than we will be ready to bring all kernel fixes which are in modified state to >= f16
libreport-2.0.12-2.fc17, abrt-2.0.11-1.fc17, btparser-0.18-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-11529/abrt-2.0.11-1.fc17,libreport-2.0.12-2.fc17,btparser-0.18-2.fc17
Package abrt-2.0.12-1.fc17, libreport-2.0.13-1.fc17, btparser-0.18-2.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.12-1.fc17 libreport-2.0.13-1.fc17 btparser-0.18-2.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11529/abrt-2.0.12-1.fc17,libreport-2.0.13-1.fc17,btparser-0.18-2.fc17 then log in and leave karma (feedback).
abrt-2.0.12-1.fc17, libreport-2.0.13-2.fc17, btparser-0.18-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.