If you did not migrate your account yet, visit https://idp-portal-info.suse.com/
| This article has been transferred to the http://wiki.opensuse.org/openSUSE:Submitting_bug_reports . Please use new location for your contributions. |
Don't create permanent links to the http://wiki.opensuse.org. It is temporary location and it will be switched back to http://en.opensuse.org after sufficient number of articles is there, or latest by July 12th, 2010.
You can help us and speed up the process by participating in creation of a new wiki that will replace the current one. See Transition guidelines for more details.
|Submitting Bug Reports - Bug Reporting FAQ - Bugs Definitions - 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 development 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.
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:
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 Factory,
- open bugs 11.2,
- open bugs 11.1,
- open bugs 11.0,
- open bugs 10.3,
- open bugs 10.2
- open bugs 10.1
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.
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 mkinitrd bug
- How to report a KDE bug
- How to report a X11-related bug
- How to report a sound-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
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.novell.com itself only.
Voting in Bugzilla
Voting in Bugzilla is intended for orientation purposes only--not for specific prioritization or resource allocation.
Reporting documentation defects
Report openSUSE documentation defects in Bugzilla (component: "Documentation") and, for released products, also add entries to:
- Errata in the openSUSE 11.2 Documentation
- Errata in the openSUSE 11.1 Documentation
- Errata in the openSUSE 11.0 Documentation
- Errata in the openSUSE 10.3 Documentation
- Errata in the openSUSE 10.2 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.
You can also participate in fixing bugs. Easiest way to start with fixing bugs are Junior Jobs. These are manually selected easy to fix examples on which you can learn how to contribute and start contributing.