English
$ rpm -q gnome-software
gnome-software-3.28.2-1.fc28.x86_64
$ rpm -q <packagename>
$ sudo dnf update --refresh
20180825-how-to-file-a-bug-cc-list.png
20180825-how-to-file-a-bug-gs-bugs.png
20180825-how-to-file-a-bug-gs.png
20180825-how-to-file-a-bug-new-bug.png
20180825-how-to-file-a-bug-new-bug-shortcut.png
20180825-how-to-file-a-bug-qa.png
*Actual results:*
*Additional info:*
*Advanced searching*: You can also use the https://bugzilla.redhat.com/query.cgi[advanced search features of the bug tracker] to narrow down your search.
However, this is not necessary.
After a bug has been filed, you should keep an eye out for any updates. 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.
Always: the issue is observed each time.
A new bug report template.
Any additional information that may be useful to the maintainer should be added here.
As bugs are reported and fixed, developers collect a set of fixes and periodically release improved versions of their software. So, before reporting an issue, it is useful to check if you are using the latest version of a software. The simplest way to get the latest version of software in Fedora is to regularly update your system. Users of Gnome/KDE and other desktop environments can use their default applications to do so. These periodically check for updates and notify users. You can also use the default package manager `dnf` to check and update your system. Only users with administrator privileges can do so:
As can be seen in the image, the https://apps.fedoraproject.org/packages/[Fedora Packages Web application] also gives other information about a package.
*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.
A software bug does not necessarily need to be a software crash. Any undesired behaviour noticed in software should be filed as a bug. The package maintainer can then look at the bug report and decide the best course of action.