|
|
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
|
|
|
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)
|
|
|
|
|
36.
|
|
|
If not enough possible duplicates are found, or you did not find a similar report, then you can force it to search for more bug reports (only if the date range is not reached.)
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:173
|
|
|
38.
|
|
|
Details of the Bug report
|
| Context: |
|
@title
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:183
|
|
|
41.
|
|
|
This page will send the bug report to the bug tracking system and will notify you when it is done. It will then show the web address of the bug report in the KDE bug tracking system, so that you can look at the report later.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:194
|
|
|
42.
|
|
|
If the process fails, you can click <interface>Retry</interface> to try sending the bug report again.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:198
|
|
|
51.
|
|
|
This crash information is not useful enough, do you want to try to improve it? You will need to install some debugging packages.
|
| Context: |
|
@info
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
reportassistantpages_base.cpp:107
|
