|
|
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
|
|
|
28.
|
|
|
We may need to contact you in the future to ask for further information. As we need to keep track of the bug reports, you need to have an account on the KDE bug tracking system. If you do not have one, you can create one here: <link>%1</link>
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:124
|
|
|
31.
|
|
|
List of possible duplicate reports
|
| Context: |
|
@title
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:140
|
|
|
32.
|
|
|
This page will search the bug report database for similar crashes which are possible duplicates of your bug. If there are similar bug reports found, you can double click on them to see details. Then, read the current bug report information so you can check to see if they are similar.
|
| Context: |
|
@info/rich
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:143
|
|
|
33.
|
|
|
If you are very sure your bug is the same as another that is previously reported, you can set your information to be attached to the existing report.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:148
|
|
|
34.
|
|
|
If you are unsure whether your report is the same, follow the main options to tentatively mark your crash as a duplicate of that report. This is usually the safest thing to do. We cannot uncombine bug reports, but we can easily merge them.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:151
|
|
|
35.
|
|
|
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 limit is not reached.)
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:155
|
|
|
36.
|
|
|
If you do not find any related reports, your crash information is not useful enough, and you really cannot give additional information about the crash context, then it is better to not file the bug report, thereby closing the assistant.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:158
|
|
|
38.
|
|
|
In this case you need to write a title and description of the crash. Explain as best you can.
|
| Context: |
|
@info/rich
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:167
|
|
|
39.
|
|
|
You can also specify your distribution method (GNU/Linux distribution or packaging system) or if you compiled the KDE Platform from sources.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:171
|
