The wikis are now using the new authentication system.
If you did not migrate your account yet, visit

openSUSE:Submitting bug reports

(Redirected from Bugs)
Jump to: navigation, search
  • Developers and experienced users: You can go directly to and report a bug.
  • Non-technical users: You may try first .
  • 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.

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.

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

Accessing Bugzilla

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:

openSUSE Leap 15.4 development version:

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:

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

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

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-support).

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 a bad 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:

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.2). 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 '' is for bugs in itself only.
  • If you know project and package, you can look it up in and click the little beetle icon [tools-report-bug.png] there to get a prefilled bugzilla entry:
    • 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.

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 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.