Although we have worked with the program for many years, we have not eliminated all bugs in the program. If you think you have found a bug in O, you should address yourself directly to one of the authors, preferably via e-mail, not to o-info. Please include a description of the exact circumstances that triggered the bug, and also what machine and which version of the program. To be able to fix the bug, we will have to be able to reproduce it. If you cannot reproduce the bug yourself, forget about it, then we will not be able to do it either. If you can reproduce it, but we can't, we may ask you to supply additional data.
A word of caution is appropriate: the open data structure of the O program gives you some very powerful capabilities, but if you don't know what you're doing, you can easily disrupt the internal datastructure in the program, making it fail immediately, or under certain circumstances. This gives you a lot of flexibility and power, but also responsibility. The program can not control the intactness of it's own datastructure, because it does not have any knowledge of what values should be present in the database. If you think you have a bug of this nature, you may try to create a fresh new database, only entering an absolute minimum of data from the old corrupt one.
O relies on access to a lot of software facilities of the host computer, for example the graphics libraries. Sometimes bugs and incompatibilities are introduced by the vendor when updating from one version of the software to the next. While we cannot be responsible for this type of bugs, we will try to provide fixes and workarounds in the following version of O.