|
|
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
|
|
|
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
|
|
|
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
|
|
|
45.
|
|
|
If you are interested into helping us to organize bug reports allowing the developers to focus on fixing the real issues, join the BugSquad (#kde-bugs on FreeNode IRC)
|
| Context: |
|
@info/rich
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
aboutbugreportingdialog.cpp:191
|
|
|
56.
|
|
|
Another debugging process is attached to the crashed application. Therefore, the DrKonqi debugger cannot fetch the backtrace. Please close the other debugger and click <interface>Reload</interface>.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
backtracewidget.cpp:194
|
|
|
62.
|
|
|
You can click the <interface>Install Debug Symbols</interface> button in order to automatically install the missing debugging information packages. If this method does not work: please read <link url='%1'>How to create useful crash reports</link> to learn how to get a useful backtrace; install the needed packages and click the <interface>Reload</interface> button.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
backtracewidget.cpp:198
|
|
|
65.
|
|
|
You could try to regenerate the backtrace by clicking the <interface>Reload</interface> button.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
backtracewidget.cpp:294
|
|
|
67.
|
|
|
You need to install the debugger package (%1) and click the <interface>Reload</interface> button.
|
| Context: |
|
@info/rich
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
backtracewidget.cpp:308
|
|
|
122.
|
|
|
<strong>Does the application crash again if you repeat the same situation?</strong>
|
|
|
i18n: file: ui/assistantpage_bugawareness.ui:93
i18n: ectx: property (text), widget (QLabel, m_reproducibleLabel)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
rc.cpp:16
|
|
|
123.
|
|
|
I did not try again
|
|
|
i18n: file: ui/assistantpage_bugawareness.ui:122
i18n: ectx: property (text), item, widget (QComboBox, m_reproducibleBox)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
rc.cpp:19
|
