English
How often is the issue observed? Usually, a good answer to this field is one of:
Here, the `package name` must be the formal name of the package.
*Help test updates*: All users can help by testing new versions of software.
More information on this can be found https://fedoraproject.org/wiki/QA:Updates_Testing[here].
Note that this requires a https://admin.fedoraproject.org/accounts/[Fedora account].
Hardware-Specific Bugs
Graphical User Interfaces
For example:
*Finding the name of the package*: If you do not know the formal package name of the software, you can use the https://packages.fedoraproject.org/[Fedora Packages Web Application] to search for it and view the list of bugs there.
Filing a bug report
Explain the issue in more detail here.
*Expected results:*
Enhancement Requests
*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.
*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:
*Description of problem:*
*Description*: More detailed information about the issue should be provided here.
It already contains a template, which is explained below.
Crashes
*Component*: This will be set to the name of the package.
*Bug tracker*: The Fedora bug tracking system at https://bugzilla.redhat.com.
Bugs are filed on https://bugzilla.redhat.com[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 https://accounts.fedoraproject.org/[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.
*Bug*: A bug is any behaviour in a software that appears unexpected/undesired.