If you find a problem in Gzz, we would like to hear about it.
The way to inform us of a problem in Gzz is reporting a bug.
On making a good bug report
First of all, see if you can reproduce that bug. This means that you should be able to list the actions required to trigger the bug again. We love bug reports that have precise (and preferably simple) instructions for reproducing the bug, but if you can't reliably reproduce the bug, report it anyway and tell us that you can't reproduce it reliably.
Then, look at the first line(s) of output that your Gzz client prints out, before it opens any windows. They should look roughly like this:
Starting gZigZag client, build: Official 0.5.1 (without modules)or like this:
Starting gZigZag client, build: Official Debian package version 0.5.1-1or like this:
Starting gZigZag client, build: Official CVS snapshot 2000-08-10T19:17:01Z (without modules)or like this:
Starting gZigZag client, build: Custom CVS Build 2000-08-08T12:35:25Z by ajk@mustiThe specifics of those lines will vary but the general format is the same. You should copy these lines precisely into your bug report so we know which version you are using. (If you have made local changes to the sources, please tell us about them too.) Then, if you have any ideas on the cause or a possible fix for the bug, include them in your bug report.
How to report the bug
Mail your report to email@example.com. Remember to specify in your mail subject that you are reporting a bug in Gzz.