GNO Bug Reports

A critical part of GNO development is user feedback. What works well? What needs improvement? What is broken? By telling GNO developers this information, you are much more likely to see improvements.

The traditional method of sending in bug reports is to email the developer. While this mechanism is simple, it has a few drawbacks:

The GNO Consortium now provides a common bug reporting and tracking system. While it is primarily intended for bug reports on the GNO base distribution, reports are also welcome on programs that are not part of the base distribution (but that still run under GNO). This system is accessible both though the web and through email.

Bug Reports -- Web Access

The recommended way to submit GNO bug reports is to use the web-based bug reporting package. There are two ways to access this system: Note that this reporting system is accessible from Lynx, but is more readable using a graphical browser. This is unfortunate, but fixing this problem will require modifications to the bug tracking software itself. This will be addressed when time permits.

While the web interface allows replies and followups to existing reports, it is also possible to send replies and followups using regular email. See the Report Followups subsection under Email Access, below.

Bug Reports -- Email Access

Initial Reports

If you prefer to send your bug reports via regular email, you can send them to If you do this method, please ensure that your subject line contains a concise description of the problem, such as
	open(2) doesn't set errno
	rm broken for HFS volumes

When sending your bug reports in email, please also include the following information, in addition to your informative subject line:

Note that bug reports to the above address will go straight into the reporting system. If your bug report contains proprietary information, you should send it to

Report Followups

If you wish to use the email interface to enter followup text on a particular, you can do it by emailing your message to, provided that your subject line follows a particular format. Specifically, the subject line must contain the text (PR#nn), where nn is the problem report number. This string must not contain any whitespace or other characters, except as shown. The parenthesis are part of the string.

The subject line may contain other text, but the above is required for the message to be recognised as a followup rather than a new problem report.