Changes in How to Write a Good Bug Report
Revision Differences of Revision 15
A very good guide (from the perspective of a programmer) and to get an idea about bug reporting itself, you can read this (long) [article](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html). ¶¶
If you are not an native english speaker (like me), there are different languages: ¶
¶
English | Português | 简体中文 | Česky | Dansk | Deutsch | Español | Français | Magyar | Italiano | 日本語 | Nederlands | Polski | Русский | 繁體中文 ¶
¶
¶
. ¶
¶
¶
##0. The easiest way to report a bug is to open up a bug report at [Launchpad](https://bugs.launchpad.net/widelands). ¶
¶
¶
On the right hand side are two possibilities: ¶
¶
* Report a bug ¶
* Ask a question ¶
¶
Therefore you will need an account on Launchpad! ¶
¶
Just fill out the head line and 'search' - maybe other bugs coming up so your bug was reported some time ago. ¶
¶
If your bug is not listed or nothing was found, please fill out the free form with the needed information (see below), scroll down and attach files (and add proper tags). ¶
¶
Some more help about Launchpad can you get [here](https://help.launchpad.net/Bugs). ¶
¶
¶
If you feel not okay with this, report the bug on our forum under "Technical Help" - Link: https://wl.widelands.org/forum/forum/1/ (btw. the internal Link description is wrong!) ¶
¶
##1. We need mandatory the following details about your configuration: ¶
¶
¶
* Operating System (OS) and patch level/kernel: ¶
* e. g.: Windows XP SP3 ¶
* e. g.: 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 ¶
* e. g.: bzr6826 ¶
* e. g.: 1:17-ppa0-bzr6827-201402020556~ubuntu12.04.1 ¶
¶
¶
##2. Describe the error / bug / false behavior as exact a possible: ¶
¶
* An meaningful headline would be a good idea. ¶
¶
* Describe what you have done or expected and what happened instead, please in detail, but not a second TLotR/Bible: ¶
¶
* e. g.: wanted to attack the enemy -> no soldier attacks / game crashed while opening up statistic details ¶
¶
¶
##2a. If you have trouble with the graphics, music, sound, ... add the hardware also in the bug report or as an attachment: ¶
¶
* Mainboard and CPU ¶
* RAM ¶
* Graphics card ¶
* SSD/HDD and extraordinary configuration (RAID ?; LVM2 ?; ...) ¶
* Network card (?) ¶
* Sound card (?) ¶
¶
* e. g.: Gigabyte GA-MA790GP-UD4H F7c w/ AMD Phenom II X4 810 + 2× 2×2048 MB AData DDR2 800 MHz; Gigabyte GV-R667D3-2GI; 64 GB AData SP900 /; 2×1 TB Seagate ST31000523AS /home (LVM2) + 1.5 TB Seagate ST31500521AS /pub; Pioneer BDR-208DBK ¶
¶
If you do NOT know the exact pieces of your machine, look either ¶
¶
* in the system management (Start --> Execute... --> compmgmt.msc --> Device Manager --> ) ¶
¶
* or in a Terminal by typing "sudo lshw > lshw.txt" ¶
¶
¶
##3. Attach save games and/or replays: ¶
You will find them dependent on your OS ¶
¶
¶
###3a. Apple Operating Systems: ¶
¶
¶
* Mac OS
* Mac OS
¶
¶
###3b. Microsoft Operating Systems: ¶
¶
* Windows XP/Vista: C:\\Documents\\[username]\\.widelands
¶
* Windows Vista:
¶
* Windows 7: ¶
¶
* Windows 8 (if you have NOT upgraded to 8.1): ¶
¶
* Windows 8.1: ¶
¶
¶
###3c. GNU/Linux: ¶
¶
¶
* /home/[username]/.widelands ¶
* tested with Ubuntu and Fedora ¶
¶
¶
##4. If you had an crash, attach the file to the bug report. The path differs according to your OS: ¶
¶
*
¶
* Microsoft OSes: C:\\Programs\\Widelands\\stdout.txt ¶
¶
* GNU/Linux: ¶
¶
¶
##5. Still more questions about bug reporting? ¶
¶
Cannot find anything on the damn machine? Struggling with my bad english? ¶
¶
Try in this order: ¶
¶
* search in the Forums ¶
* search on Launchpad for questions ¶
* ask them on chat ¶
* ....