Search the Community

We now have a public bug tracker. I have disabled the creation of new entry's. And will disable the bug tracker soon. Therefore we created a few rules and guidelines on the bug tracker. Please, only create entries for real bugs, i.e. parts of the application that are not working as intended. What is not meant to go into the bug tracker: wishes and ideas for new features requests to change existing features configuration issues and other user failures complaints and rants requests to handle certain bugs with higher/lower priority bumping up bugs issues with applications without a project in the bug tracker Unfitting entries in the bug tracker will be closed or deleted without notice. How to report a bug: make sure to use the newest version, check here. Only reports for the most recent versions can be processed make sure the bug is not already reported make sure that it is not just a configuration issue. Search the forum and wiki for possible solutions Essential parts of a bug report: Issue Title: a meaningful title that describes the bug as good as possible (version number and name of the application are not necessary here, they can be derived by the category the bug is in) Exact description of the bug. I.e. what does not work? Try to keep it exact but short. Most important: exact steps to reproduce the issue. It might be necessary to report even every key press and mouse click in the exact order. Please include all circumstances. A support.zip is mandatory. For DVBViewer Pro best produce a support.zip with debug.log. I.e. run DVBViewer with Window Start menu > Programs > DVBViewer > Support > DVBViewer Pro (Debug Mode) and then do the steps to reproduce the error from part 3 of your bug report and reproduce the issue described in part 2. After that create the support.zip which will contain the debug.log file. A good example is http://www.DVBViewer.tv/forum/tracker/issue-15-searching-in-the-channel-list-editor-dosent-work/ Meanings of the Issue Information: Issue ID: no meaning for our projects, currently Version: the most recent version for which the bug can be reproduced. Will be filled automatically upon reporting/confirming a bug Fixed in: version the bug is fixed in. Might be a future version number, i.e. it is fixed for an internal test version and therefore will be fixed in the next release version Status: The most important field Unconfirmed: Default value for new bugs Need more Info / Unreproducible: The supplied information are not enough to reproduce the bug. Everybody that experiences the described issue should have a look what might be missing in the steps to reproduce the issue and the description of the circumstances. Support.zip files from multiple affected computers / installations usually help, too. Confirmed: At least one beta tester or developer can reproduce the bug. Usually means that no further user comments are necessary. Fixed: The bug has been resolved. The next release should not have the issue anymore. Duplicate: The bug was already reported, the entry is closed and a link to the previous bug will be inserted. Please go there and see if you can add information of value. Please report bugs only once. Won't fix: The developers decided not to resolve the issue. Most probably the effort necessary to resolve the bug is much too high for the severity of the bug. Closed: The bug has been in state "Need more Info" for multiple weeks, but nobody delivered any information. So there can't be that many people affected. Another possibility is that the bug has not been confirmed since multiple versions and might have been fixed by accident. Not a Bug: An issue that should not have gone to the bug tracker. Might be an configuration issue or a feature request. Both should go to the forum. I am experiencing a bug that is already reported. What to do? This depends on the state of the bug in the bug tracker. You can click on "Issue Confirmation" in the bug tracker. Usually you don't have to do anything else. Just wait for the next release. One exception is, if the bug is in state Need more Info / Unreproducible. If so, please scan the information that already has been given by other users and see if you can add anything of value. There is a second exception: If the bug has not been reported for your version, i.e. Version contains a lower number. That means the bug has not been reproduced in the most recent version. In this case you might report that you can reproduce the bug in the newer version and if so, how (see above). I am still not sure what to do. If you are unsure, please first ask in the forum. If the discussion with other users leads to the result that you really found a bug and are not suffering from configuration issues or similar, people will tell you to open a bug in the bug tracker.