|
|
14.
|
|
|
This backtrace appears to be of no use. 
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
|
|
|
17.
|
|
|
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.
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
|
|
|
23.
|
|
|
KDE crash handler gives the user feedback if a program crashed
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
main.cpp:43
|
|
|
43.
|
|
|
<p>Do you want to generate a backtrace? This will help the developers to figure out what went wrong.</p>
<p>Unfortunately this will take some time on slow machines.</p><p><b>Note: A backtrace is not a substitute for a proper description of the bug and information on how to reproduce it. It is not possible to fix the bug without a proper description.</b></p> |
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
toplevel.cpp:135
|
|
|
48.
|
|
|
Backtrace Not Possible
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
toplevel.cpp:216
|
