|
|
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)
|
|
|
|
|
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
|
|
|
14.
|
|
|
actions you were taking inside or outside the application
|
| Context: |
|
@info/rich crash situation example
|
|
|
|
|
radnje koje ste izvodili unutar ili izvan programa;
|
|
Translated by
Chusslove Illich
|
|
|
|
Located in
aboutbugreportingdialog.cpp:75
|
|
|
15.
|
|
|
documents or images that you were using and their type/format (later if you go to look at the report in the bug tracking system, you can attach a file to the report)
|
| Context: |
|
@info/rich crash situation example
|
|
|
|
|
dokumente koje ste koristili i njihov tip i format (posle podnošenje izveštaja u sistem za praćenje grešaka, možete priložiti i fajl uz njega);
|
|
Translated by
Chusslove Illich
|
|
|
|
Located in
aboutbugreportingdialog.cpp:77
|
|
|
16.
|
|
|
widgets that you were running
|
| Context: |
|
@info/rich crash situation example
|
|
|
|
|
vidžete koji su se izvršavali;
|
|
Translated by
Chusslove Illich
|
|
|
|
Located in
aboutbugreportingdialog.cpp:80
|
|
|
17.
|
|
|
the url of a web site you were browsing
|
| Context: |
|
@info/rich crash situation example
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:96
|
|
|
18.
|
|
|
or other strange things you notice before or after the crash.
|
| Context: |
|
@info/rich crash situation example
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
bilo kakve neobičnosti koje ste primetili pre ili posle pada.
|
|
Translated by
Chusslove Illich
|
|
|
|
Located in
aboutbugreportingdialog.cpp:83
|
|
|
19.
|
|
|
Screenshots can be very helpful. 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:99
|
|
|
20.
|
|
|
Conclusions
|
| Context: |
|
@title
|
|
|
|
|
Zaključci
|
|
Translated by
Chusslove Illich
|
|
|
|
Located in
aboutbugreportingdialog.cpp:106
|
|
|
21.
|
|
|
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
|
|
|
|
|
Prema sastavu sakupljenih podataka o padu, i odgovorima koje ste dali na prethodnoj stranici, pomoćnik će vam reći vredi li prijavljivati pad.
|
|
Translated by
Chusslove Illich
|
|
|
|
Located in
aboutbugreportingdialog.cpp:108
|
