GNO Bug Reports

If you wish to report a defect or suggest an enhancement, please use the GNO Bugzilla.

Before you file a bug report, please ensure that it is actually a defect in GNO. The bug tracker is NOT a general support mechanism, such as if you're having problems trying to figure out how to do a particular task.

Second, having concluded that what you have is actually a bug (or enhancement request), please search bugzilla to ensure that it has not already been reported (or suggested). Note that there is more than one product supported by bugzilla.gno.org. Ensure that you are filing bugs under GNO itself and not one of the other products hosted by the GNO Consortium.

Be aware that the GNO Bugzilla uses self signed certificates. If you're getting warnings from your browser about the certificates, help is available (just note that the site name is for https://bugzilla.gno.org as opposed to https://lists.gno.org).

Writing an Effective Bug Report

For an excellent article on submitting bug or defect reports in general (that is, for any software product), please see Simon Tatham's How to Report Bugs Effectively.

For GNO in particular, please ensure that for bug reports you're reporting at least the following information:

• A summary of the problem.
• A detailed description of the problem.
• Instructions on how to produce the problem.
• With which distribution did you observe the problem? If it is a released version, report the GNO version (eg: v2.0.6). If it is with something that is based on current code you built from the source repository, report the version as "current"
• Which component is affected? The actual list is configured in bugzilla, however it will be something like the following:
  • Documentation
  • Utilities
  • The GNO Shell
  • The Kernel
  • Libraries and Header Files
• If you are reporting a problem with a utility or library routine, include the name of the utility (or routine). If it's available, also quote the version. This is often given as an rVersion resource on programs and libraries.
• If your problem is with a library routine, give a short program which exhibits the problem.
• You can attach supporting documents, source files, etc as attachments in bugzilla.