|
|
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
|
|
|
14.
|
|
|
the URL of a web site you were browsing
|
| Context: |
|
@info/rich crash situation example
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:81
|
|
|
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
|
|
|
25.
|
|
|
If the crash is worth reporting but the application is not supported in the KDE bug tracking system, you will need to directly contact the maintainer of the application.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:111
|
|
|
30.
|
|
|
The KWallet dialog may appear when pressing Login to save your password in the KWallet password system. Also, it will prompt you for the KWallet password upon loading to autocomplete the login fields if you use this assistant again.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:133
|
|
|
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
|
