|
|
5.
|
|
|
In order to generate a useful bug report we need some information about both the crash and your system. (You may also need to install some debug packages.)
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:53
|
|
|
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 formed internationally.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:60
|
|
|
10.
|
|
|
If you can, describe in as much detail as possible the crash circumstances, and what you were doing when the application crashed (this information is going to be requested later.) 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:72
|
|
|
12.
|
|
|
documents or images that you were using and their type/format (later if you go to look at the report in the bug tracking system, you can attach a file to the report)
|
| Context: |
|
@info/rich crash situation example
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:77
|
|
|
17.
|
|
|
Screenshots can be very helpful sometimes. 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:85
|
|
|
19.
|
|
|
This page will generate a "backtrace" of the crash. This is information that tells the developers where the application crashed.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:92
|
|
|
20.
|
|
|
If the crash information is not detailed enough, you may need to install some debug packages and reload it (if the <interface>Install Debug Symbols</interface> button is available you can use it to automatically install the missing information.)
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:95
|
|
|
21.
|
|
|
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)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:99
|
|
|
22.
|
|
|
Once you get a useful backtrace (or if you do not want to install the missing debugging packages) you can continue.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:101
|
|
|
24.
|
|
|
Using the quality of the crash information gathered, and your answers on the previous page, the assistant will tell you if the crash is worth reporting or not.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:108
|
