Then click on the Report a new bug in the component in the Fedora Product link in the bottom-left corner of the page. This leads you on the Bugzilla page for this particular package. From this point, there are two ways to complete your filling of the bug: Or, if you know what the package name is, you can point your browser to (replace with the name of the package). On the home page, you can click the enter a new bug report link. Some programs also have dedicated files or directories in /var/log which are worth checking. It is always useful to check /var/log/messages (for everyone) and ~/.xsession-errors (for desktop users) to see if there are any errors or warnings related to your problem. ![]() ![]() See "Tips by type of bug" below for specific guidance. See BugZappers/FindingDuplicates for more details. If you are experiencing the bug in a more recent version of Fedora than reported in the bug, this is useful to mention. you have more detailed debugging information, or a different hardware or software configuration which means a hardware-specific or configuration-specific bug is more widespread than previously thought). It's not generally useful to file "I'm experiencing this bug, too" comments, unless there are specific details which might be helpful in tracking down the cause (e.g. Or you can use to look for specific bugs for a package (replace with the name of the package you are checking). ![]() The easiest way is to do a keyword search. It's important to search Bugzilla to make sure your bug hasn't already been reported. Very common known bugs are listed at Bugs/Common. It does not mean that the software is more buggy.īugZappers/UnderstandingBugzilla has a few technical notes that may help Bugzilla make more sense. If a particular software package is heavily used, it is more likely that users will find bugs and/or suggest enhancements to it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |