Description of problem: Every time I log in I see abrt warning me about kernel oops. It does not count as the next occurrence of the same incident, it is always displayed as a new incident (a new item in the list). I have reported it (I promise!). I don't want to report it over and over again. I also don't need to see the warning icon each time I login. I would like to have the possibility to select the kernel crash item and choose "don't report any other crashes from this application". That would be great. Version-Release number of selected component (if applicable): abrt-plugin-sqlite3-0.0.11-2.fc12.x86_64 abrt-plugin-bugzilla-0.0.11-2.fc12.x86_64 abrt-desktop-0.0.11-2.fc12.x86_64 abrt-addon-python-0.0.11-2.fc12.x86_64 abrt-addon-ccpp-0.0.11-2.fc12.x86_64 abrt-plugin-logger-0.0.11-2.fc12.x86_64 abrt-0.0.11-2.fc12.x86_64 abrt-addon-kerneloops-0.0.11-2.fc12.x86_64 abrt-libs-0.0.11-2.fc12.x86_64 abrt-gui-0.0.11-2.fc12.x86_64 abrt-plugin-kerneloopsreporter-0.0.11-2.fc12.x86_64 How reproducible: always
First, I'd advise you to bump to v1.0.0, now in testing. The kernel oops detection likely to be enhanced, could you attach those two "different" kernel traces, please? Well, reporting "over and over" makes some sense, it gives kernel devs info about how often this oops is occurring. I understand that manual reporting is kinda pitta here, automatic reporting as it was in old kerneloops-client makes sense.
(In reply to comment #1) > I understand that manual reporting is > kinda pitta here, automatic reporting as it was in old kerneloops-client makes > sense. The automatic reporting is being implemented as we speak, so it should be in ABRT soon. The version 1.0 has some improvements in kerneloops scanner which should fix a lot of false alarms. You can try to install it using yum: $ yum update abrt --enablerepo=updates-testing Jirka
After updating to abrt-1.0.0-1.fc12.x86_64 I have seen no new kernel warning on system startup. Perfect. Of course that this enhancement may be still valid in some cases, that's up to your consideration.
(In reply to comment #2) > (In reply to comment #1) > > I understand that manual reporting is > > kinda pitta here, automatic reporting as it was in old kerneloops-client makes > > sense. > > The automatic reporting is being implemented as we speak, so it should be in > ABRT soon. The version 1.0 has some improvements in kerneloops scanner which > should fix a lot of false alarms. You can try to install it using yum: > > $ yum update abrt --enablerepo=updates-testing > > Jirka I implemented automatic kerneloops report yesterday. It's in git repository.
abrt-1.0.1-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/abrt-1.0.1-1.fc12
abrt-1.0.1-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12994
Since abrt-1.0.7-1.fc12 is already in stable updates, I think this bug may be closed.