2. Tails
3. wiki/src/doc/first_steps/bug_reporting.*.po
4. Chinese (zh)
5. Browse

1 / 5

/ 5

All strings

• Not translated strings • state:empty
• Strings needing action • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with labels • has:label
• Strings with context • has:context
• Strings needing action without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Translated string
• Age of string
• Number of words
• Number of comments
• Number of failing checks
• Key

	English	Chinese (zh)
	[[!meta title="Reporting an error"]]
	In this documentation we use the term *bug* to refer to a software error.
	Reporting bugs is a great way of helping us improve Tails.
	Remember that **the more effectively you report a bug**, the more likely we are to fix it.
	[[!toc levels=2]]	[[!toc levels=2]]
	<h1 id="already-known">Check if the bug is already known</h1>
	Have a look at:
	the [[list of known issues|support/known_issues]]	[[已知的问题列表|support/known_issues]]
	the [[!tails_gitlab groups/tails/-/milestones desc="list of things that will be fixed or improved in the next release"]]
	<h1 id="useful-bug-report">How to write a useful bug report</h1>
	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](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html), by Simon Tatham.
	<h1 id="whisperback">Use WhisperBack</h1>
	**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|bug_reporting#special-cases]].**
	WhisperBack will help you fill-up a bug report, including relevant technical details and send it to us encrypted and through Tor.
	Start WhisperBack
	To start <span class="application">WhisperBack</span>, choose <span class="menuchoice"> <span class="guimenu">Applications</span>&nbsp;▸ <span class="guisubmenu">System Tools</span>&nbsp;▸ <span class="guimenuitem">WhisperBack Error Reporting</span></span>.