Reporting Bugs

We'd like to hear about any bugs or unexpected behavior you find in Vidalia. If you think the bug you found is related to Tor instead of Vidalia, please do not create a ticket on our bug tracker. Instead, see the Tor support documentation for further assistance.

Please read the following steps before creating your bug report:

1. Before Adding Your Bug Report

First, use the Search page to search for previous tickets related to your problem or the wiki for additional support documentation. If someone else has already reported the bug, there may be a workaround or the status of a fix listed in the ticket.

If you don't find any relevant tickets or support documentation, check the Roadmap and our TODO to see if it's something we already know about and are currently working on.

2. Adding Your Bug Report

Note: Due to spammers abusing our ticket system, we have restricted the ability to create and edit tickets to only logged in users. Eventually we want to allow everyone to create their own accounts, but for now you can use the username vidalia and the password vidalia.

If you are sure you have found a new bug, then please create a new ticket. If you have multiple, unrelated bugs to report, please do not put them all on one ticket; create one ticket for each new bug. Be sure to include the following information:

• Your operating system (be specific)
• Which version of Vidalia you're using (be specific; saying "latest" is not a valid version number)
• Which version of Tor you're using (be specific; saying "latest" is not a valid version number)
• If you are running Tor as an NT service on Windows, include that information as well
• Any configuration changes you may have made through Vidalia or in Tor's torrc
• If you're running Vidalia in a language other than English, specify which one
• If there are relevant messages in Vidalia's message log, those would be helpful, too
• If you get any error message boxes, include their exact content
• If you're reporting a crash bug, a stack trace is the likely best piece of information you can provide
• If you built Vidalia from source, specify which version of Qt you are using (you can find out by selecting About from Vidalia's tray menu)
• Steps to reproduce the problem

Please do not set the Milestone field. Vidalia's developers will assign your ticket to a milestone when they decide which Vidalia release will contain a fix for the reported bug or enhancement.

If you can think of other information that may be useful for us to reproduce the bug, please include it as well. You should also add an e-mail address at which you can be contacted to the CC: field on the ticket, in case we need more information from you.

This page is also good to read and will help you write better bug reports, which, in turn, helps us fix bugs faster.

3. After You Have Added Your Bug Report

After you have added your bug report, please don't disappear! We may have questions or need more information from you before we can track down the cause of the bug. If you don't add your e-mail address to the CC: field on the ticket, please at least check back periodically until you are satisfied that we have fixed the bug you reported.