VirtualBox

Version 72 (modified by Michael Thayer, 12 years ago) ( diff )

Another re-write of the bug tracker guidelines to be more positive and try to encourage reporters to be active themselves.

Bugtracker

This site offers a public bugtracker. In case you encounter problems with VirtualBox or have other suggestions for improvements, you can use this facility to report those issues, which will then be called a "ticket". Each such ticket receives a unique number that you can later refer to in order to see if any progress was made, or add comments to it.

Please be aware that we (the core team) receive more bug reports than we can read, let alone resolve, so we tend to focus on tickets which seem important to us - because they impact a lot of people, or some people very severely, or paying customers, or look like something which can be fixed quickly. Please also remember that developers and reporters are on an equal footing - just as we cannot make demands of you, neither can you demand that we work on a particular issue, however important it may seem to you.

Remember also though that VirtualBox is open source software. That means that if we are not able to work on a particular issue someone else or you yourself can do so and we can integrate the solution if it does not impact other people. A good bug ticket is a great aid for whoever chooses to work on a problem.

So bearing that in mind, there are a number of things you can do to improve the chances of getting your problem solved.

  • Do some research (e.g. using search engines, our ​forums and existing bug tickets) before creating a ticket. Your problem may well be known; someone (we or others) may have solved it or be working on a solution; you may find out enough to solve it yourself.
  • You should find out and understand as much about the problem as possible before creating the ticket, so that you can create as clear, as complete and as concise a description as possible for whoever (us, someone else, yourself) attempts to fix the problem. Consider using the forums to get help with this.
  • Describe as precisely as you can how to reproduce the problem, bearing in mind that it may be triggered by something special on your own computer system. It is often next to impossible for a developer to fix a problem that they cannot reproduce. It may help to find other people with the same problem and compare notes.
  • Choose a summary carefully. The bug tracker and ticket notifications are mainly seen by (busy) developers, and unless a summary catches their eye and looks related to the things they as an individual work on the ticket may not even be read.
  • Please stay polite, relevant and on-topic. Try to avoid creating tickets for issues which are already being worked on, but do also try to avoid commenting on a ticket if you are not sure that your problem is the same (and not just similar) - if the ticket contains a link to a forum topic, consider going there first. Offensive or unrelated comments and tickets take time away from other things and sap our and other people's motivation; in extreme cases we can delete them.

Note: To create new tickets, you must have registered with this site and be logged in with your user name and password. Use the "Register" and "Login" links at the top right for that. If you add a comment to an existing ticket, you will receive e-mail notification every time that ticket is updated.

Then, use these links to access the bugtracker:

Note: See TracWiki for help on using the wiki.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette