|
|
6.
|
|
|
Bug Reporting Assistant Steps Guide
|
| Context: |
|
@title
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:57
|
|
|
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)
|
|
|
|
|
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)
|
|
|
|
|
34.
|
|
|
If you are very sure your bug is the same as another that is previously reported, you can open the previously reported crash in the bug tracking program by clicking on <interface>Bug report page at the KDE bug tracking system</interface>. You can then add any new information that you might have.
|
| Context: |
|
@info/rich
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(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
|
|
|
37.
|
|
|
Do not worry if you cannot find a similar bug report or you do not know what to look at. The bug report database maintainers will look at it later. It is better to file a duplicate then to not file at all.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
|
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
|
|
|
70.
|
|
|
This application is supported in the KDE bug tracking system. You can manually report this bug at <link>%1</link>. Click <interface>Finish</interface> to close the assistant.
|
| Context: |
|
@info
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
drkonqiassistantpages_base.cpp:309
|
|
|
71.
|
|
|
This application is not supported in the KDE bug tracking system. You can manually report this bug to its maintainer at <link>%1</link>. Click <interface>Finish</interface> to close the assistant.
|
| Context: |
|
@info
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
drkonqiassistantpages_base.cpp:316
|
