|
3.
|
|
|
Could not generate a backtrace as the debugger '%1' was not found.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
backtrace.cpp:83
|
|
6.
|
|
|
Backtrace saved to %1
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:103
|
|
7.
|
|
|
Cannot create a file in which to save the backtrace
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:107
|
|
13.
|
|
|
Unable to create a valid backtrace.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:146
|
|
14.
|
|
|
This backtrace appears to be of no use. ![](/@@/translation-newline)
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:147
|
|
15.
|
|
|
Loading backtrace...
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:156
|
|
16.
|
|
|
The following options are enabled:
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:179
|
|
17.
|
|
|
![](/@@/translation-newline)
As the usage of these options is not recommended - because they can, in rare cases, be responsible for KDE problems - a backtrace will not be generated. ![](/@@/translation-newline)
You need to turn these options off and reproduce the problem again in order to get a backtrace.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:181
|
|
18.
|
|
|
Backtrace will not be created.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:186
|
|
20.
|
|
|
System configuration startup check disabled.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
debugger.cpp:216
|