openSUSE:Submitting bug reports
tagline: From openSUSE
- Developers and experienced users: You can go directly to http://bugzilla.opensuse.org/ and report a bug.
- Non-technical users: You may try first http://forums.opensuse.org .
- Want to learn: It is not the easiest thing that you ever did, but it is not rocket science either. Please read the text below that has basic instructions how to report a bug.
In general: 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.
You're also welcome to fix the bug directly as explained in the fixing bugs documentation.
To report a bug on Bugzilla visit a page from the list below corresponding to your openSUSE version.
First you will see the login page. Bugzilla and openSUSE wiki logins are the same.
The rolling release version of openSUSE, Tumbleweed:
The in-development version of openSUSE, Leap 42.3:
The following are officially maintained versions, maintained by openSUSE Maintenance Team that consists of SUSE security team and volunteers from community.
Next links can be used for openSUSE infrastructure, Build Service and all wiki servers:
This is for beta versions of commercial products SLES and SLED:
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 for Tumbleweed
- Open bugs for Leap 42.2
- Open bugs for Leap 42.1
- Open bugs for 13.2
- Open bugs for 13.1
and look through the list.
Reporting a bug
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).
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. For Leap packages that are inherited from SLE, just file the bug for Leap. The bug will be forwarded to the correct maintainer from there.
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. Furthermore having separated issues in separated bug reports is a precondition to handle the issues independently because different issues usually require different people to get them analyzed and resolved.
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 report Factory bug
- 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 printing-related bug
- How to report a GNOME bug
- How to report AppArmor bugs
- How to report a Mozilla / Firefox bug
- How to report LibreOffice bug
- How to report OpenOffice.org bug
- How to report a Samba bug
- How to report a Wireless connectivity bug
- How to report a Font Issue
- How to report a Wicked 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.opensuse.org itself only.
- If you know project and package, you can look it up in build.opensuse.org and click the little beetle icon </> there to get a prefilled bugzilla entry:
- 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.
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.
You can also participate in fixing bugs as explained on the fixing bugs documentation. The 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.