|
|
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
|
|
|
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
|
|
|
26.
|
|
|
If the crash is listed as being not worth reporting, and you think the assistant has made a mistake, you can still manually report the bug by logging into the bug tracking system. You can also go back and change information and download debug packages.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:114
|
|
|
27.
|
|
|
Login into the bug tracking system
|
| Context: |
|
@title
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:122
|
|
|
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
|
|
|
29.
|
|
|
Then, enter your username and password and press the Login button. You can use this login to directly access the KDE bug tracking system later.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:130
|
|
|
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
|
|
|
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
|
