In this documentation we use the term bug to refer to a software error.
Reporting bugs is a great way of helping us improving Tails.
Remember that the more effectively you report a bug, the more likely we are to fix it.
Have a look at:
- the list of known issues
- the list of things to do
- the list of things that will be fixed or improved in the next release
- The first aim of a bug report is to tell the developers exactly how to reproduce the failure, so try to reproduce the issue yourself and describe how you did that.
- If that is not possible, try to describe what went wrong in detail. Write down the error messages, especially if they have numbers.
- Write clearly and be precise. Say what you mean, and make sure it cannot be misinterpreted.
- Be ready to provide extra information if the developers need it. If they did not need it, they would not be asking for it.
You can also refer to the great How to Report Bugs Effectively, by Simon Tatham.
WhisperBack is an application written specifically to report bugs anonymously from inside Tails. If you are not able to use WhisperBack, see the special cases.
WhisperBack will help you fill-up a bug report, including relevant technical details and send it to us encrypted and through Tor.
To start WhisperBack, choose .
WhisperBack lets you give plenty of useful information about your bug:
- Summary a summary of the bug, try to be short, clear and informative
- Name of the affected software
- Exact steps to reproduce the error
- Actual result and description of the error
- Desired result
You can also have a look at the technical details to include in your bug report. It will give us information about your hardware, your version of Tails and the startup process.
We answer requests in:
Requests not in English might take longer to answer. Imperfect English is welcome :)
Giving us an email address allows us to contact you to clarify the problem. This is needed for the vast majority of the reports we receive as most reports without any contact information are useless. But note that it also provides an opportunity for eavesdroppers, like your email or Internet provider, to confirm that you are using Tails.
You can also indicate an OpenPGP key corresponding to this email address. You can either give:
- a key ID, if the key is available on public key servers
- a link to the key, if the key is available on the web
- a public key block, if the key is not publicly available
Once you are done writing your report, send it by clicking the Send button.
Once your email has been sent correctly you will get the following notification: Your message has been sent.
You might not always be able to use WhisperBack. In those cases, you can also send your bug report by email directly.
Note that if you send the report yourself, it might not be anonymous unless you take special care (e.g. using Tor with a throw-away email account).
WhisperBack won't be able to send your bug report.
The following steps can be used as an alternative method:
- In Tails, start WhisperBack
- In the bug report window, expand "technical details to include"
- Copy everything in the "debugging info" box
- Paste it to another document (using gedit for instance)
- Save the document on a USB stick
- Boot into a system with Internet connection and send your report
For troubleshooting instructions in case Tails fails to start, refer to our installation instructions on: