Examples

Differences between revisions 2 and 6 (spanning 4 versions)
⇤ ← Revision 2 as of 2005-11-03 21:18:56 →
Size: 433
Editor: 167_220_103_66-WIFI_HOTSPOTS
Comment: edits
← Revision 6 as of 2006-12-11 23:09:09 → ⇥
Size: 1129
Editor: rouben
Comment: Added sample bug to the list.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from Bugs/ExamplesDraft
Line 10: Line 11:
  * refer to ["Bugs/CommonTasksDraft"] for tasks that are common   * refer to ["Bugs/CommonTasks"] for tasks that are common

 * 49175, [https://bugs.launchpad.net/distros/ubuntu/+source/ubiquity/+bug/49175 dapper install freeze at "loading kernel"]
  * The end-user's bug report was very superficial and didn't include the necessary information. The bug was rejected with a "canned" message.
  * Due to lack of information, the bug also seemed to be more of a support request than a bug. I suspected that the problem was caused by a bad ISO download or an improper burn, which would fall under tech support rather than debugging. As such a combination of canned responses from Bugs/Responses was used (needs info and tech support).
Line 13: Line 18:
Back to HelpingWithBugs Back to '''["HelpingWithBugs"]'''.[[BR]][[BR]]
[:CategoryBugSquad]

This page lists examples of bugs where the assignee and the bug triage team did a good job of clarifying the problem and identifying the actual bug.

If you see a nice example of good bug work, be sure to list it here.

Bugs

  • Bug number, Link
    • brief outline, of how the bug was processed
    • remarkable aspects
    • refer to ["Bugs/CommonTasks"] for tasks that are common

  • 49175, [https://bugs.launchpad.net/distros/ubuntu/+source/ubiquity/+bug/49175 dapper install freeze at "loading kernel"]

    • The end-user's bug report was very superficial and didn't include the necessary information. The bug was rejected with a "canned" message.
    • Due to lack of information, the bug also seemed to be more of a support request than a bug. I suspected that the problem was caused by a bad ISO download or an improper burn, which would fall under tech support rather than debugging. As such a combination of canned responses from Bugs/Responses was used (needs info and tech support).

Back to ["HelpingWithBugs"].BRBR [:CategoryBugSquad]

Bugs/Examples (last edited 2008-08-06 17:00:54 by localhost)