Distance Support, Updates and Extras

Reporting a Bug in Distance

This page contains information about how to report a bug in Distance.

If you are having problems with Distance, please first check the manual and readme file (ReadMe.rtf) carefully, then search the Bugzilla database of known problems. Note, when searching for bugs make sure to search both open and closed bugs, this is easiest done in the simple search engine by changing the status to “All ”. If you have an older version of Distance you may wish to check the bug has not yet been resolved in the latest version. Finally, you may want to check the archives of the distance-sampling e-mail list. Once you have exhausted these possibilities, please submit new bugs to the Bugzilla database.

Report a Bug using Bugzilla:

Before you can report a bug you will need to create an account with Bugzilla, this allows you to track the bugs you report.

Please submit only one bug per report.

Be Precise and clear so the bug can be reproduced.

Inform us of any non-standard UK set up on your machine (E.g. which language edition of Windows; which regional settings you're using).

Clearly separate fact from speculation

If possible, upload an example project demonstrating the bug. (Please remove all non-relevant analyses/designs before uploading.)

No bug is too trivial to report - small bugs may hide big bugs!

Further information on reporting a bug using Bugzilla can be found in the Bugzilla Guide.

Spam Prevention in Bugzilla:

To help prevent spam to Bugzilla users, all email addresses stored in Bugzilla are now displayed only if you are logged in. If you are logged out, only the part before the "@" of the email address is displayed. This includes bug lists, viewing bugs, the XML format of a bug, and any other place in the web interface that an email address could appear.

However you should note that email addresses are not filtered out of bug comments. The WebService still returns full email addresses, even if you are logged out.

Distance home page