|
|
6.
|
|
|
Bug Reporting Assistant Steps Guide
|
| Context: |
|
@title
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:57
|
|
|
7.
|
|
|
This assistant will guide you through the crash reporting process for the KDE Bug Reports Database Site. All the information you enter on the bug report must be in English, if possible, as KDE is developed internationally.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:59
|
|
|
9.
|
|
|
This page will generate a backtrace of the crash. This is information that tells the developers where the application crashed. If the crash information is not detailed enough, you may need to install some debug packages and reload it. You can find more information about backtraces, what they mean, and how they are useful at <link>%1</link>
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
|
12.
|
|
|
In this page you answer some questions about the crash context, and note whether you are willing to help the developers in the future. To do this, you will need to open a KDE Bug tracking system account. This is strongly encouraged, as often a developer may need to ask you for clarification. Also, you can track the status of your bug report by having email updates sent to you.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
|
13.
|
|
|
If you can, describe in as much detail as possible, the crash circumstances, and what you were doing when the application crashed. You can mention:
|
| Context: |
|
@info/rich
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:87
|
|
|
19.
|
|
|
Screenshots can be very helpful. You can attach them to the bug report after it is posted to the bug tracking system.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:99
|
|
|
22.
|
|
|
If the crash is worth reporting, and the application is supported in the KDE bug tracking system, you can click <interface>Next</interface>. However, if it is not supported, you will need to directly contact the maintainer of the application.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:108
|
|
|
26.
|
|
|
Then, enter your username and password and press the Login button. Once you are authenticated, you can press Next to continue. You can use this login to directly access the KDE bug tracking system later.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:127
|
|
|
29.
|
|
|
In this step you need to write at least four (4) words to describe and identify the crash. You do not need to use the application name, since that will be automatically sent. This text will be used to search for similar crashes already reported in the database, to help you and others find them later. Also, this text will be used to start the title of the future bug report. You can change this title later. Some examples: toolbar vanishes then plasma crashes, or (konqueror) crash on a site with CSS. Note that you do not need to use the word crash, since that is already part of the report.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
|
31.
|
|
|
Bug Report Possible Duplicate list
|
| Context: |
|
@title
|
|
|
|
|
(no translation yet)
|
|
|
