Submitting Bug Reports
From openSUSE
| | Need Help? |
|
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, read about severities and priorities, as well as our Testing information for new testers.
Contents |
Accessing Bugzilla
To access Bugzilla, visit the version page.
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:
Searching for Bugs
Before you begin, check to see if the bug has already been reported, especially in the list of Most Annoying Bugs. You can also search for open bugs 11.0, open bugs 10.3, open bugs 10.2 or open bugs 10.1 and look through the list.
Reporting a Bug
All openSUSE/SUSE Linux 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). |
Some software components have special instructions for bug reporting, which you can find here:
- How to attach an error log when an application crashes
- How to attach a log for bugs related to YaST or the installation
- How to attach a log for bugs related to Zypper or OpenSUSE Updater Applet
- How to attach a log for bugs related to ZENworks/rug
- How to report a GCC bug
- How to report a kernel bug
- How to report a KDE bug
- How to report a X11-related bug
- How to report a GNOME bug
- How to report a bug in Kontact's Novell GroupWise support
- How to report SaX2 bugs
- How to report suspend bugs
- How to report AppArmor bugs
- How to report a Mozilla / Firefox bug
- How to report OpenOffice.org bug
- How to report a boot loader (grub) bug
- How to report a Samba bug
- How to report a Security bug
- How to report a HAL bug
- How to report a Wireless connectivity bug
| 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. |
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 this page.
List Bugzilla reports with votes
Reporting Documentation Defects
Report openSUSE documentation defects in Bugzilla (component: "Documentation") and, for released products, also add entries to Errata in the openSUSE 11.0 Documentation or Errata in the openSUSE 10.3 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.

