openSUSE:Submitting bug reports
- 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.
Creating Bugzilla account
If you have already an OBS login then you should be all set. Otherwise, please create your account at https://idp-portal.suse.com/univention/self-service/#page=createaccount
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 transactionally-updated Micro Service OS, MicroOS:
The CNCF Certified Kubernetes distribution based on MicroOS, Kubic
Regular Release, stable versions:
Note: Since 15.4 openSUSE Leap is built on top of binaries from SUSE Linux Enterprise. Bug reports against these inherited packages are tracked in PUBLIC SUSE Linux Enterprise bugzilla products and where priority is set by SLE Release Manager.
- openSUSE Leap 15.4
- PUBLIC SUSE Linux Enterprise Server 15 SP4
- PUBLIC SUSE Linux Enterprise Desktop 15 SP4
- PUBLIC SUSE Linux Enterprise High Availability Extension 15 SP4
openSUSE Leap 15.5 development version:
- openSUSE Leap 15.5
- PUBLIC SUSE Linux Enterprise Server 15 SP5
- PUBLIC SUSE Linux Enterprise Desktop 15 SP5
- PUBLIC SUSE Linux Enterprise High Availability Extension 15 SP5
Next links can be used for openSUSE infrastructure, Build Service and all wiki servers:
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:
Reporting a bug
In most cases openSUSE bugs should go into the product "openSUSE".
The exception is Leap, where packages that are inherited from SLE need to be tracked in PUBLIC SUSE Linux Enterprise products (see links above), community maintained packages are expected to be reported under the product openSUSE Distrbution. If unsure you can simply open all Leap bugs under product openSUSE Distribution and Leap Release Manager, Screening team, or person responsible for triage in individual teams will move it under to the respective PUBLIC SLE product.
Please always try to choose the right product when reporting a bug, it will speed up resolution of the issue.
Some software components have special instructions for bug reporting, which you can find here:
- How to report AppArmor bugs
- How to report a Documentation bug
- How to report Factory bug
- How to report a Font Issue
- How to report a GCC bug
- How to report a GNOME bug
- How to report a KDE bug
- How to report a kernel bug
- How to report a LibreOffice bug
- How to report a dracut bug
- How to report a MinGW bug
- How to report a Mozilla / Firefox bug
- How to report an OpenOffice.org bug
- How to report a printing-related bug
- How to report a Samba bug
- How to report a Snapper bug
- How to report a X11-related bug
- How to report a Wicked bug
- How to report a Wireless connectivity bug
- 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 a Virtualization bug in the KVM stack, also including Kubevirt
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 Leap versions you can download are handled in the component 'openSUSE Distribution'. In the version field, select the correct version ("Leap X.X", where X.X is the version you found the bug in, e.g. 15.5). If you are using milestone and release candidate versions, it is very important to specify this in the bug report. Providing just the product version is not enough here.
- Bug reports for Tumbleweed are handled in the component 'openSUSE Tumbleweed'. If you don't use the latest version of Tumbleweed and/or know which version introduced the bug, please specify this in the bug report.
- The product 'openSUSE.org' is for 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.