Step 2: Follow up on filed reports
Step 2: Check for already filed bugs
Step 1: Filing a new bug
Step 1: Check for the latest version
Step 0: Create a Bugzilla account
Sometimes: the issue occurs, but not each time.
*Severity, Hardware, OS*: These fields are optional and need not be set.
Searching the Fedora Packages Web Application for Gnome Software.
*QA*: Quality assurance is the process of ensuring that the software works as intended.
*Package*: Each software that is available in Fedora has a formal package name that is used by the bug tracker and other infrastructure tools.
Packages can be searched using the https://src.fedoraproject.org/[Fedora dist-git].
Only once: the issue was only observed once.
Once the improved version of the software has passed the QA process, the bug will automatically be closed. Congratulations!
More reading
*Maintainer*: A body of volunteers that takes care of the software packages provided in Fedora.
These are referred to as "package maintainers".
They keep track of bugs, help with issues, and generally act as middlemen between the developers of the software and Fedora users.
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.
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 https://packages.fedoraproject.org/[Fedora Packages Web application] lists the currently reported bugs for all packages. There is also a convenient shortcut that can be used.
If no updates are made to the bug in a week or two, you should also feel free to comment asking for any information. Sometimes maintainers who receive many bug reports can miss notification e-mails. A polite comment will send them a new notification.
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:
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 https://packages.fedoraproject.org/[Fedora Packages Web application].
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html[A general introduction on how to file good bugs (available in multiple languages)].