Currently Online

Latest Posts

Changes in How to Write a Good Bug Report

Editor Comment

typos


Revision Differences of Revision 18

For very in-depth guidelines on how to report bugs in a way that assists the programmer, check out this [article](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html). ¶

If you are not a native English reader (like me), here are a number of options: ¶

English | Português | 简体中文 | Česky | Dansk | Deutsch | Español | Français | Magyar | Italiano | 日本語 | Nederlands | Polski | Русский | 繁體中文 ¶


. ¶


##0. The easiest way to report a bug is to craft a bug report at [Launchpad](https://bugs.launchpad.net/widelands). ¶

You will need to have a Log-In on Launchpad. ¶

On the right hand side are two options: ¶

* Report a bug ¶
* Ask a question ¶

Before filling out a Bug Report, use the Search function to see if your problem has already been addressed. ¶

If your bug is not listed or nothing was found, click Report a Bug to fill out the form with the needed information (see below), then scroll down and attach files. Do not forget to add the proper tags. ¶

For more help specifically with Launchpad, check [here](https://help.launchpad.net/Bugs). ¶


If you are unable or unwilling to use Lanchpad, report the bug to "Technical Help" - Link: https://wl.widelands.org/forum/forum/1/ (btw. the internal Link description is wrong!) ¶

##1. We need ALL of the following information to try and address the problem: ¶


* 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 specifically as possible: ¶

* Think about your headline; try to be succinct as well as descriptive. ¶

* Describe what you did and what you expected to happen, as well as what actually occurred. Again, be descriptive, but try not to write the next installment of A Song of Ice and Fire or Linux from scratch. ¶

* e. g.: wanted to attack the enemy -> no soldier attacks / game crashed while opening up statistic details ¶


##2a. If you have trouble with the hardware/ plug-ins (graphics, music, sound, etc.), be sure to indicate this 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 exactly which hardware elements you are referring to, check the following: ¶

* in the system management (Start --> Execute... --> compmgmt.msc --> Device Manager --> ) ¶

* in Terminal by typing "sudo lshw > lshw.txt" ¶


##3. Attach save games and/or replays. The way to do this is dependent on your OS: ¶


###3a. Apple Operating Systems: ¶


* Mac OS X: ¶


###3b. Microsoft Operating Systems: ¶

* Windows XP/Vista: C:\\Documents\\[username]\\.widelands ¶

* 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 a crash, attach the file to the bug report. The path differs according to your OS: ¶

* Mac OS X: ¶

* Microsoft OS's: C:\\Programs\\Widelands\\stdout.txt ¶

* GNU/Linux: ¶


##5. Still have more questions about bug reporting? ¶

Cannot figure it out on the damn machine? Struggling with my bad English/ this guide? ¶

Try in this order: ¶

* search in the Forums ¶
* search on Launchpad for questions ¶
* ask them on chat ¶
* raise hands in despair, listen to Despair, fall on the floor, watch as everyone else becomes a dinosaur