Changes in How to Write a Good Bug Report

Old Title

Editor Comment

First steps for a good bug report

Revision Differences of Revision 1

0. The easiest way to report a bug is to open up a bug report at https://bugs.launchpad.net/widelands. Therefor you will need an account on Launchpad! ¶
On the right hand side are two possibilities: ¶
- Report a bug ¶
- Ask a question ¶
¶
1. We need mandatory the following details about your configuration: ¶
¶
- Operating System (OS) and patch level/kernel: ¶
e. g.: Windows XP SP3 / Xubuntu 12.04.3, Linux xubuntu 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan 30 17:24:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ¶
¶
- Widelands release: ¶
e. g.: 17 / bzr6826 / 1:17-ppa0-bzr6827-201402020556~ubuntu12.04.1 ¶
¶
¶
2. Describe the error / bug / false behavior as exact a possible: ¶
2a. An meaningful headline would be a good idea. ¶
2b. Describe what you have done or expected and what happened instead, please in detail but not a second bible: ¶
e. g.: wanted to attack the enemy -> no soldier attacks / game crashed while opening up statistic details ¶
¶
3. Attach save games and/or replays: ¶
You will find them dependent on your OS ¶
¶
3a. Apple Operating Systems: ¶
3aa. Mac OS (9): ¶
3ab. Mac OS X: ¶
¶
3b. Microsoft Operating Systems: ¶
3ba. Windows XP: ¶
C:\Documents\[your_name]\.widelands ¶
3bb. Windows Vista: ¶
3bc. Winodws 7: ¶
3bd. Windows 8 (if you have NOT upgraded to 8.1): ¶
3be. Windows 8.1: ¶
¶
3c. GNU/Linux: ¶
3ca. G/K/X/Ubuntu: /home/[your_name]/.widelands ¶
3cb. whatever Linux you use, feel free to fill up the missing paths...! :-) ¶
¶
4. If you had an crash, add the file also: ¶
4a. Apple OS: ¶
4b. Microsoft OS: C:\Programs\Widelands\stdout.txt ¶
4c. GNU/Linux: