Bug Reporting (2) How to write a good report

A few tips on how to write good bug reports:

• write in English: you can switch every KDE application to English in the Help menu. That can help you in explaining what happens.
• be specific: one bug per report only! Do not mix problems in the same report.
• be clear: explain the steps that lead to the bug so that we can reproduce them easily
• include screenshots: a picture is worth many words so attach a screenshot to the bug report (using KSnapshot for example). Do not link to an external web link which can expire, use the Attachments link at the bottom of the bug report.
• include the backtrace within the bug report as a comment, it makes it easier to find duplicates for us (do not attach the backtrace as a text file)
• clearly separate facts from speculation: only describe what happens. For a design problem, include a mock-up if possible.

If you are testing trunk or the beta, if you kept your precedent settings, sometimes you will want to check with a new user or by setings a new $KDEHOME (and restarting your user). Do not delete your $KDEHOME as you will maybe need the current files to compare with the new ones and also you would lose your settings!

The KDE forum has a new section about the Releases and in particular about the Betas for 4.6!