Introduction

Bugs relating to <package name/category> typically fall into X categories:

1. User interface bugs - require a detailed description of the issue, steps to reproduce and screen captures where appropriate.
2. Crasher bugs - Log files from the crash incident are required to track down these.
3. Hardware specific bugs - The developers may not have access to the hardware that triggers this bug. Certain log files and command outputs can help
4. Package selection - Help to find the right package (may be specific to category -- a bug filed as ubiquity may in fact be a casper d-i bug, an xorg bug may be an xorg-driver bug, etc.)

How to file

Useful for bug-filers and as a boiler-plate advice for triagers.

Debugging procedure

Specific to this type of package.

Known bugs

Description of known issues, how to recognise them and stock responses/actions.

Open

Closed

Non-bugs

How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses.

Also see

• DebuggingProcedures

CategoryBugSquad