This document describes how to create useful bug reports for crashes of KDE applications.
A crash or (system crash) in computing is a condition where a program (either an application or part of the operating system) stops performing its expected function and also stops responding to other parts of the system. More information at Wikipedia
A good crash report consists of two parts: a description of how to reproduce the crash and a backtrace of the crash. With any of those elements missing, it is very hard (if not impossible) for developers to tackle the problem.
A useful description should contain everything that you were doing prior to the crash. It should not just say "it crashed".
Examples: Did you click on a button, did you open a particular website or file which caused problems? These little details, which may look useless to you, may be useful for the developers, so just write them down.
A more insightful article on how to write good bug descriptions is available at this link, please read that before reporting bugs.
The KDE Platform version is an important detail that is often missing in bug reports.
If you do not know what KDE Platform version are you using, you can get it:
Qt: 4.6.0 KDE Development Platform: 4.4.0 kde4-config: 1.0
|The crash reporting assistant integrated in KDE 4.3 and later automatically includes the KDE version in your report.|
For several applications it can be useful to have specific details inside the bug reports:
A backtrace basically describes what was happening inside the application when it crashed, in a way that developers may track down where the mess started. They may look meaningless to you, but they might actually contain a wealth of useful information.
|If you are providing a backtrace in a report which does not belong to you, consider that the report could be unrelated to your crash, even when the symptoms are the same. In such cases, just attach the backtrace as a file, so the bug triagers can check it and say if it is the same crash or not|
To generate a new backtrace you need the application to crash again. This can be achieved repeating the same steps and situation that leaded to the original crash.
The application crashes and the KDE Crash Handler dialog appears
Screenshot of the KDE Crash Handler dialog