linux package hook needs updating

Bug #614421 reported by Leann Ogasawara
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
Fix Released
Canonical Kernel Team

Bug Description

Binary package hint: apport

Opening a bug based on an email sent to the kernel-team mailing list:

"I just filed a bug against the kernel in Maverick using Apport, and there are some bugs I noticed, and thought this was more appropriate than a Launchpad bug (since there's really no package for this kind of bug report).

1) Using the guided-tagging, I selected "Graphics" and my bug was tagged with 'graphics' instead of 'kernel-graphics', which is what the tag should be according to Kernel/Tagging [1].

2) On Launchpad, the info page asks you to: "Depending on the nature of your bug report following the instructions at will make your bug report even more complete. Thanks!" However, that link is broken. I'm assuming it should point to [2], or even better [3], since the KernelTeam pages are being deprecated.

Other than those two, the Apport process for kernel bugs looks really really cool, especially the tag promps. Nice work JFo/others! :)


Changed in apport (Ubuntu):
assignee: nobody → Canonical Kernel Team (canonical-kernel-team)
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Matt Zimmerman (mdz) wrote :

1) The current hook looks correct with respect to the tags (it uses kernel-graphics). I haven't tried it, but I think it will work as expected

2) This sounds like a bug in the per-package bug reporting guidelines, which need to be fixed in Launchpad, rather than apport

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

I changed the Debugging link, but I think that text needs to be updated a bit more. I have taken an action to rewrite this text.

Matt, I agree with you, the tagging seems to have been addressed. I'm going to close this bug as fixed since the main issues have been fixed.



Changed in apport (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers