DebuggingBanshee
|
Size: 3010
Comment:
|
Size: 2283
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| = 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. 1. Crasher bugs - Log files from the crash incident are required to track down these. 1. Hardware specific bugs - The developers may not have access to the hardware that triggers this bug. Certain log files and command outputs can help 1. 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.) |
|
| Line 16: | Line 9: |
| = Bug tags = Bug tags specific to the package or area should be included here for reporters so they can tag their bug report. It will also be useful for triagers. The Bugs/Tags wiki page should then be modified to include these tags. |
|
| Line 22: | Line 12: |
| In depth debugging procedures for this particular package or subsystem. This usually is information about the log files to gather and what to look for in them. | 1. Debugging Banshee from a terminal, please run "banshee --debug" and attach all output information 2. Debugging latest release from daily ppa repository, url is at https://launchpad.net/~banshee-team/+archive/banshee-daily 3. Hardware not detected and further information at http://live.gnome.org/Banshee/LibgpodTransition |
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Contents |
How to file
Please fill all your bugs using "ubuntu-bug banshee" or from banshee menu.
Debugging procedure
- Debugging Banshee from a terminal, please run "banshee --debug" and attach all output information
Debugging latest release from daily ppa repository, url is at https://launchpad.net/~banshee-team/+archive/banshee-daily
Hardware not detected and further information at http://live.gnome.org/Banshee/LibgpodTransition
How to Triage
Information that will facilitate the triaging of bugs for this package or subsystem. Remind triagers of the bug tags in use for this particular package.
Stock Reply
A stock reply to be used for initial bug reports basically asking for the stuff in "How to file". The Bugs/Responses page should include this reply.
How to Forward
In the event that the package or subsystem has an upstream bug tracker this section should contain detailed steps to forward a bug to that tracker. Some packages may just link to the general "How to Forward" page for another bug tracker like Gnome's bugzilla or freedesktop.org's bug tracker.
Known bugs
Description of known bug reports that may receive duplicates and how to recognise them. This information should be obtained by looking for bugs tagged as 'metabug'.
Open
Bug |
Subject |
Symptom |
The subject from LP |
This bug can be identified by ... |
Closed
Bug |
Subject |
Symptom |
The subject from LP |
This bug can be identified by ... |
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.
DebuggingBanshee (last edited 2013-02-25 00:42:36 by c-76-25-23-72)