real kerneloops and suspend/hibernate/resume bugs are hard to separate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt | ||
Jaunty |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
Binary package hint: apport
When submitting a real kerneloops we end up with a tags of <arch> apport-kerneloops, for suspend/
We are treating the kerneloops report type in apport as a kernelerror type and we should probabally therefore make the tags reflect that. One option might be to make the general tag apport-kernel and then manually add the apport-kerneloops only to the actual oopses that migth work better.
oops: apport-kernel apport-kerneloops
s/r/h: apport-kernel resume hibernate
The other might be to add a subsiduary tag for panics:
oops: apport-kerneloops panic-oops
s/r/h: apport-kerneloops resume hibernate
Changed in apport (Ubuntu Jaunty): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in apport (Ubuntu Jaunty): | |
assignee: | nobody → pitti |
status: | Triaged → In Progress |
Changed in apport (Ubuntu Jaunty): | |
status: | In Progress → Fix Committed |
I agree that "apport-kernel" would be nicer as a general tag. I'm just concerned that this breaks backwards compatibility wrt. to LP searches and tools which search for this, thus right now I tend to go with the second alternative. Is that okay for you?