Cómo presentar un error

The purpose of this document is to give step by step instructions on filing bugs in Fedora. For more information about using Bugzilla, see the Bugs section of the Quick Docs.

A software bug does not necessarily need to be a software crash. Any undesired behaviour in software can be filed as a bug. The package maintainer can then look at the bug report and decide the best course of action.

Anyone can file bugs: All users are encouraged to file any bugs they run into. Bug filing is not limited to only software developers.


Hay uno pocos términos que se usan habitualmente en este documento:

  • Gazapo: Un gazapo es cualquier comportamiento del software inesperado/indeseado.

  • Rastreador de gazapo: El sistema de rastreo de gazapos de Fedora en https://bugzilla.redhat.com.

  • Paquete: Cada software disponible en Fedora tiene un nombre de paquete formal que se usa por el rastreador de gazapos y otras herramientas de infraestructura. Los paquetes se pueden buscar usando Fedora dist-git.

  • Mantenedor: Un cuerpo de voluntario que están al cuidado de los paquetes de software suministrados en Fedora. Son llamados "mantenedores de paquete". Ellos mantienen el rastro de los gazapos, ayudan con cuestiones y generalmente actúan como intermediarios entre los desarrolladores de software y los usuarios de Fedora.

  • QA: La garantía de calidad es el proceso para asegurar que el software trabaja como está previsto.

  • Bodhi: La Aplicación Web QA de Fedora.

Antes de rellenar un gazapo

Ask Fedora — the community support forum — is a good place to start if you’re not sure if you’ve encountered a bug. Sometimes what is perceived as a bug is a misunderstanding or a question. The Ask Fedora community can help you figure out if you’ve encountered a bug — and if it’s specific to Fedora or is in the upstream package.

Step 0: Check the Common Issues page

We maintain a list of common issues. Check this site first to see if your issue has been reported — and if a solution exists.

Paso 1: Compruebe la última versión

A medida que se informan y solucionan gazapos, los desarrolladores recogen un conjunto de correcciones y periódicamente lanzan versiones mejoradas de su software. Así que, antes de informar de una cuestión, es útil comprobar si está utilizando la última versión del software. La forma más sencilla de obtener la última versión del software en Fedora es actualizar regularmente su sistema. Los usuarios de Gnome/KDE y otros entornos de escritorio pueden usar sus aplicaciones predeterminadas para hacer esto. stas periódicamente comprueban las actualizaciones y lo notifican a los usuarios. Usted puede hacer uso del administrador de paquetes predeterminado dnf para comprobar y actualizar su sistema. Sólo los usuarios con privilegios de administrador pueden hacerlo así:

$ sudo dnf update --refresh

Step 2: Check for already filed bugs

If you are using the latest version of the software available in Fedora, then it is likely that the bug has either not been reported, or has been reported but a fix has not yet been released. So, it is useful to search the list of already reported bugs before filing a new report. The Fedora Packages Web application provides a link the open bugs for a package. There is also a convenient shortcut that can be used.

https://bugz.fedoraproject.org/<package name>

Here, the package name must be the formal name of the package.

Finding the name of the package: If you do not know the formal package name of the software, you can use the Fedora Packages Web Application to search for it and view the list of bugs there.
20180825 how to file a bug gs
Figure 1. Searching the Fedora Packages Web Application for Gnome Software.
Advanced searching: You can also use the advanced search features of the bug tracker to narrow down your search. However, this is not necessary.

If a bug report has already been filed describing the issue, you should provide any extra information you may have. If there is nothing more to add to the report, you should "CC" (carbon-copy) yourself to the report to receive any updates. This can be done by clicking on the "Save changes" button when the "Add me to CC list" option is checked as shown below:

20180825 how to file a bug cc list
Figure 2. The CC list contains all users that should be notified when any updates are made to the report.

Filing a bug report

Step 0: Create a Bugzilla account

Use your Fedora account: You can use your Fedora account to sign into Bugzilla. This is preferred, since your Fedora account can also be used to log into all other Fedora services.

Bugs are filed on Fedora’s bugzilla instance, and you must have an account there to file bugs or interact with them. An account requires a valid e-mail address and can be created here (click "Register"). The bug tracker will only send e-mail notifications about bugs that a user is involved in. No other e-mails will be sent.

Step 1: Filing a new bug

If a bug report for the particular issue has not already been filed, you should file a new one. The easiest way to file a new report is using the "File a new bug" drop down from the right hand side bar in the Fedora Packages Web application.

20180825 how to file a bug new bug shortcut
Figure 3. The Fedora Packages Web Application provides a convenient shortcut to file new bugs.

This redirects to a new bug report template on the bug tracker. The image below shows a new bug template:

20180825 how to file a bug new bug
Figure 4. A new bug report template.

The following fields need to be set:

  • Component: This will be set to the name of the package.

  • Version: You should set this to the version of Fedora that you observed the bug on.

  • Summary: You should provide a useful short summary of the issue here.

  • Description: More detailed information about the issue should be provided here. It already contains a template, which is explained below.

  • Attachment: Files that provide more information of the issue can be uploaded with the bug report using the button here. E.g,, screen-shots, log files, screen recordings.

  • Severity, Hardware, OS: These fields are optional and need not be set.

Description of problem:

Explain the issue in more detail here.

Version-Release number of selected component (if applicable):

The version of the package should be specified here. Once the package name is known, the version can be obtained by using the rpm command:

$ rpm -q <packagename>

For example:

$ rpm -q gnome-software

How reproducible:

How often is the issue observed? Usually, a good answer to this field is one of:

  • Always: the issue is observed each time.

  • Sometimes: the issue occurs, but not each time.

  • Only once: the issue was only observed once.

Issues that occur always are easiest for developers to diagnose, since they may also be able to replicate it on their machines to collect more information. If an issue only happens sometimes, developers must spend more time and effort to understand what causes the problem. If an issue was only observed once, it is even harder to debug.

Detailed bug reports make bugs easier to fix: If possible, you should try to investigate what steps cause the issue to happen and provide these steps in the next section:
Submit a report even if unsure: If you aren’t sure of what to fill in, you should still submit the bug report. Maintainers can follow up with questions to gather more information.

Steps to Reproduce:

These enable other users to verify the bug, and they also inform the developers of what specific steps cause the issue. It makes it much easier for them to look at the source code and pick out the bits that may be faulty.

Actual results:

What is observed when the issue occurs?

Expected results:

What does the user expect that should happen if the software behaved correctly?

Additional info:

Any additional information that may be useful to the maintainer should be added here.

Step 2: Follow up on filed reports

After a bug has been filed, you should keep an eye out for any updates. The bug status workflow documentation describes the different statuses a bug may have. An e-mail notification of any new comments to the report will be sent to everyone involved in the bug report---the reporter, other users, and the maintainer. Often, maintainers will comment with queries to gather more information on the issue. Sometimes other users that experience the same issue may also add more information.

Ask for instructions: If the maintainers ask for more information but it is unclear how it should be gathered, it is perfectly OK to ask the maintainers for explicit instructions.
E-mail notifications: The notifications are sent from bugzilla@redhat.com. You should keep an eye out for e-mails from this address, and add it to your "no-spam" lists.

Step 3: Test updates

A well reported bug will often be fixed, and the maintainer will make an improved version of the software available to Fedora users. Bodhi will add a comment to the report when this happens. You can help the maintainer by confirming if the improved version works better in the Bodhi.

20180825 how to file a bug qa
Figure 5. Bodhi Application adds comments informing users of an update that should fix the bug.
Help test updates: All users can help by testing new versions of software. More information on this can be found here. Note that this requires a Fedora account.

Once the improved version of the software has passed the QA process, the bug will automatically be closed. Congratulations!

Advice for specific bug types


If you have experienced a program crash, it will almost certainly be necessary to include a stack trace with your bug report. Crashes are often difficult to reproduce and even more difficult to fix, so the more information you can provide, the better. You will probably need to install -debuginfo RPMs so your stack trace will have useful debugging symbols. See the following pages for more information:

Enhancement Requests

Most enhancement requests should be filed upstream. If the software is missing a feature you think it should have, you generally want to file that in the upstream project’s bug tracker. Feature requests in Fedora Linux are generally changing defaults, enabling disabled-by-default features, etc.
  • When filing an enhancement request in Bugzilla, add the keyword Future Feature to the report. The Keyword should be added right after submitting the bug. You will see the Keyword input box then. Make sure you supply enough information and rationale for your enhancement requests to be considered.

  • The Fedora Project has the objective to be a platform built exclusively from free and open-source software. Suggestions to include support for proprietary or other legally encumbered software is not constructive. See the list of forbidden items page for details about this.

  • If you want to make a new feature happen on your own create a wiki page for your feature and get it accepted. See more on the Changes Process.

  • Requests for new packages to be added to Fedora should not be filed in Bugzilla.

Graphical User Interfaces

If you are having trouble with a graphical user interface (GUI), it often helps to include a screenshot or a screencast showing the bug in action. This helps developers find the exact place in the code which is causing the bug, and helps communicate what is going wrong when it is difficult to reproduce (for example, machine-specific layout problems).

Hardware-Specific Bugs

A strong indication of a hardware-specific bug is that other people with different hardware should be able to reproduce the bug, but can’t. They also usually involve code that specifically interacts with a peripheral, such a webcam, video card, printer, or sound card (so for instance, it is uncommon for bugs affecting the user interface of a word processor or desktop calculator to be hardware-specific).

If you suspect your bug has something to do with the specific hardware you have, it will be necessary to identify the hardware so targeted action can be taken.

PCI and PCI-E devices found by the kernel can be listed with lspci.

USB devices found by the kernel can be listed with lsusb.

You may also find mention of specific devices or drivers in your system logs (run journalctl).


We pay special attention to security-sensitive bugs. Read the Reporting a Security Vulnerability] page to understand the special process of opening a security bug.