I thought this was supposed to be fixed, but we're still seeing reports from abrt 2.0.7 where it's filing a bug, and then filing a second one when there's a follow-on oops in the same session.
see bug 786263 and bug 786264 for example.
786264 is fallout from the first failure, so not worth filing.
abrt allows G W flags to be reportable. turn it off?
Author: Nikola Pajkovsky <email@example.com>
Date: Wed Feb 15 14:22:44 2012 +0100
rhbz#786280 - do not turn off G W flags
Signed-off-by: Nikola Pajkovsky <firstname.lastname@example.org>
'G' is kind of an irrelevant flag. It means 'not tainted by non-gpl modules'. I don't know why they chose to do that instead of just printing nothing.
'w' means a warning has already occurred. We only care about the first one, which abrt should have already filed.
abrt-2.0.9-1.fc17, libreport-2.0.10-1.fc17 has been submitted as an update for Fedora 17.
Package abrt-2.0.9-1.fc17, libreport-2.0.10-1.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.9-1.fc17 libreport-2.0.10-1.fc17'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
abrt-2.0.10-1.fc17,libreport-2.0.10-2.fc17 has been submitted as an update for Fedora 17.
abrt-2.0.10-1.fc17, libreport-2.0.10-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.