Reports the same oops again and again

Bug #345483 reported by Matt Zimmerman on 2009-03-19
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kerneloops (Ubuntu)
Medium
Unassigned
Nominated for Karmic by mommentmal

Bug Description

Binary package hint: kerneloops

kerneloops does not seem to have any mechanism to avoid reporting the same oops more than once. If there is an oops in syslog, it will be reported every time kerneloops starts up (e.g. at system startup).

Matt Zimmerman (mdz) on 2009-03-19
Changed in kerneloops (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Martin Olsson (mnemo) wrote :

It's useful to keep track of how often each oops happens and if it's suddenly fixed etc. Certain oops might actually be one off events that happen due to some obscure race conditions while others happens all the time on boot or while doing a certain action. For triage, it's important to be able to keep track of these. I agree that it needs to be as unobtrusive as possible though.

On Tue, Mar 24, 2009 at 03:20:48PM -0000, martin wrote:
> It's useful to keep track of how often each oops happens and if it's
> suddenly fixed etc. Certain oops might actually be one off events that
> happen due to some obscure race conditions while others happens all the
> time on boot or while doing a certain action. For triage, it's important
> to be able to keep track of these. I agree that it needs to be as
> unobtrusive as possible though.

For kerneloops.org, I agree, every oops should be reported as they are
measuring frequency.

For Launchpad bugs, these should only be reported once per unique oops. For
bonus points, if there is an existing bug for the oops, kerneloops could
increment the "affects me too" counter.

--
 - mdz

James Westby (james-w) wrote :

Hi,

I think my kerneloops/apport changes will alleviate this somewhat, as even if
kerneloops keeps reporting the same oops to apport then apport should only
prompt the user once.

Fixing this in kerneloops would obviously be better, and shouldn't be too hard.

Thanks,

James

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers