[%# The contents of this file are subject to the Mozilla Public # License Version 1.1 (the "License"); you may not use this file # except in compliance with the License. You may obtain a copy of # the License at http://www.mozilla.org/MPL/ # # Software distributed under the License is distributed on an "AS # IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or # implied. See the License for the specific language governing # rights and limitations under the License. # # The Original Code is the Bugzilla Bug Tracking System. # # The Initial Developer of the Original Code is Netscape Communications # Corporation. Portions created by Netscape are # Copyright (C) 1998 Netscape Communications Corporation. All # Rights Reserved. # # Contributor(s): Eli Goldberg # Gervase Markham # Vera Horiuchi # Claudius Gayle # Peter Mock # Chris Pratt # Tom Schutter # Chris Yeh #%] [% PROCESS "global/field-descs.none.tmpl" %] [% INCLUDE global/header.html.tmpl title = "Vinux $terms.Bug Writing Guidelines" %]

Effective [% terms.bug %] reports are the most likely to be fixed. These guidelines explain how to write such reports.

Principles

Preliminaries

  1. Reproduce your [% terms.bug %] using a recent build of the software, to see whether it has already been fixed.
  2. Search [% terms.Bugzilla %], to see whether your [% terms.bug %] has already been reported.

Notes for Screen Reader Users

Reporting a New [% terms.Bug %]

If you have reproduced the [% terms.bug %] in a recent build and no-one else appears to have reported it, then:

  1. Choose "Enter a new [% terms.bug %]"
  2. Select the product in which you've found the [% terms.bug %]
  3. Fill out the form. Here is some help understanding it:

Component: In which sub-part of the software does it exist?
This field is required. Click the word "Component" to see a description of each component. If none seems appropriate, look for a "General" component.

When reporting a [% terms.bug %] against a Vinux Distribution, component represents the Edition of the distribution. Use "CD", if this does not seem to apply.

version: Select the appropriate version where the [% terms.bug %] was found. For the Vinux Distribution product, select the oldest version where the [% terms.bug %] was found. Due to the major changes with the Vinux 3.3 oneiric release and beyond, it may be necessary to submit a Vinux 3.3 [% term.bug %] report to be resolved in Vinux 4.0 and a second report if it exists on previous versions. This may require two separate solutions and the new release will definitely be assigned a higher priority. Long Term Support (LTS) versions will also recieve a higher priority.

Advanced Fields

If you have enabled the Advanced Fields toggle, it will allow you to enter information about a similar bug reported against another bug reporting system for another package from another project. These are important fields for Vinux! Much of the work in developing Vinux is based on patched and updated packages from the upstream projects. These fields allow us to track the progress of a bug through this process. Note it is usually necessary to also report the same bug to the upstream project, like orca.

Suspected Package - version:Enter the name and version of the suspected package for which the remote bug was reported to the other project. An example would be gnome-orca 3.3.3.

Even if a related bug has not yet been reported to another project, if you have a package that you suspect may be where the problem lies, enter it's name and version here.

Package bug URL: Enter the URL of the bug report against the suspect package on the project's bug reporting system. In Firefox while viewing the related bug report, this can be obtained by pressing Control + l, followed by Control + C to place it in your clipboard. Then paste into this field with Control + v, usually in another Tab or window.

Package Bug Status: The status for the bug on the project's remote bug reporting system. It is planned that this will be retreived automatically.

Resolved in Ubuntu: Use this drop down list to indicate that this bug is now resolved in Ubuntu. Select in which series (i.e. Ubuntu 12.04 precise). The default is "---", which indicates that this bug still exists in the main Ubuntu distributions.

Details

Summary: How would you describe the [% terms.bug %], in approximately 60 or fewer characters?
A good summary should quickly and uniquely identify [% terms.abug %] report. It should explain the problem, not your suggested solution.

Description: The details of your problem report, including:

Overview: More detailed restatement of summary.

Drag-selecting any page crashes Mac builds in the NSGetFactory function.

Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the [% terms.bug %]. Include any special setup steps.

1) View any web page. (I used the default sample page, 
resource:/res/samples/test0.html)

2) Drag-select the page. (Specifically, while holding down 
the mouse button, drag the mouse pointer downwards from any 
point in the browser's content region to the bottom of the 
browser's content region.)

Actual Results: What the application did after performing the above steps.

The application crashed.

Expected Results: What the application should have done, were the [% terms.bug %] not present.

The window should scroll downwards. Scrolled content should be selected. 
(Or, at least, the application should not crash.)
Build 2006-08-10 on Mac OS 10.4.3

Additional Builds and Platforms: Whether or not the [% terms.bug %] takes place on other platforms (or browsers, if applicable).

Doesn't Occur On Build 2006-08-10 on Windows XP Home (Service Pack 2)

Additional Information: Any other useful information.

For crashing [% terms.bugs %]:

  • Windows: Note the type of the crash, and the module that the application crashed in (e.g. access violation in apprunner.exe).
  • Mac OS X: Attach the "Crash Reporter" log that appears upon crash. Only include the section directly below the crashing thread, usually titled "Thread 0 Crashed". Please do not paste the entire log!

Double-check your report for errors and omissions, then press "Commit". Your [% terms.bug %] report will now be in the [% terms.Bugzilla %] database.

[% INCLUDE global/footer.html.tmpl %]