openSUSE:Submitting bug reports

Bugs

Submitting bug reports - Bug reporting FAQ - Bugs definitions - Most annoying bugs - Testing

The openSUSE project includes a growing volunteer network of Linux users and developers who participate in the ongoing creation and improvement of openSUSE by testing Tumbleweed releases. This team of testers has a common mission: they improve the world's most usable Linux distribution by finding and constructively reporting relevant bugs.

We report bugs, submit enhancements reports, or provide patches in Bugzilla, the openSUSE bug tracking system. By searching the system and providing clear, accurate details, we give developers an easy way to reproduce the defect and find quick solutions.

If you want to join the team of bug reporters, check out the openSUSE bug reporting FAQ for information.

Accessing Bugzilla

To report a bug on Bugzilla visit the version page from the list below.
First you will see the login page. Bugzilla and openSUSE wiki logins are the same.

Here is the list of bugs related to openSUSE projects:

openSUSE bug statistics

You may use helper javascripts in your Opera or Firefox (with Greasemonkey extension) to make your work with Novell Bugzilla more comfortable.

Searching for bugs

Before you begin, check to see if the bug has already been reported.

You can also search for:

and look through the list.

Reporting a bug

All openSUSE bugs should go into the product openSUSE. Always choose the right product when reporting a bug. At this time, the public Bugzilla is not intended for the enterprise products.

Bugzilla is no replacement for support. Before reporting a bug, make sure that it is really a bug. If in doubt, discuss it on the mailing lists first (opensuse-factory or opensuse).

For all versions: When reporting a bug, please use one report for each defect you want to report. Using a single bug report to address several problems at once is really not a good idea because it makes it difficult to track the progress on each item.

Selecting the correct component and version number when reporting a bug

Choosing the wrong product or component causes inefficient handling of your report, because it is initially assigned to the wrong people. Or it makes us wonder whether an already-fixed bug could possibly reappear in certain cases, which also creates unnecessary work. Choosing the correct product, component, and version is vital for us to quickly reproduce (and finally solve) your problem. So please be careful here.

All openSUSE versions you can download here are handled in the component 'openSUSE X.X' (X.X is the version you found the bug in, e.g. 11.0). If you are milestone and release candidate versions, it is very important to specify this in the version field of Bugzilla. Providing just the product version is not enough here.

The product 'openSUSE.org' is for bugs in this Wiki system on opensuse.org and bugs in bugzilla itself only.

If you know project and package, you can look it up in build.opensuse.org and click the little beatle icon []</> there to get a prefilled bugzilla entry:
- product=openSUSE.org
- classification=7340
- component=3rd party software
- assigned_to=bugowner of the package
- short_desc=project:name/package_name: what happened

Voting in Bugzilla

Voting in Bugzilla is intended for orientation purposes only--not for specific prioritization or resource allocation.

For further information about voting, refer to voting page.
List Bugzilla reports with votes

Reporting documentation defects

Please report openSUSE documentation defects in Bugzilla (component: "Documentation").

The man pages are maintained upstream as part of a corresponding source package or the global package called "man-pages"; the openSUSE documentation department is not responsible for these documents. If you find an inaccuracy in these man pages, take the time to report the issue upstream. At the end of the man page, find the bug reporting address.

Fixing bugs

You can also participate in fixing bugs. Easiest way to start with fixing bugs are minor issues and submitting the fixes for review.