|
|
48.
|
|
|
Password:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../kde/apport-kde.py:363
|
|
|
49.
|
|
|
Collecting Problem Information
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../kde/apport-kde.py:463
|
|
|
50.
|
|
|
The collected information can be sent to the developers to improve the application. This might take a few minutes.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../kde/apport-kde.py:466
|
|
|
51.
|
|
|
Uploading Problem Information
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../kde/apport-kde.py:513
|
|
|
52.
|
|
|
The collected information is being sent to the bug tracking system. This might take a few minutes.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../gtk/apport-gtk.ui.h:19 ../kde/apport-kde.py:516
|
|
|
53.
|
|
|
Apport
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../gtk/apport-gtk.ui.h:1 ../kde/apport-kde.py:383 ../kde/apport-kde.py:553
|
|
|
55.
|
|
|
Do not put the new traces into the report, but write them to stdout.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:48
|
|
|
56.
|
|
|
Start an interactive gdb session with the report's core dump (-o ignored; does not rewrite report)
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:55
|
|
|
58.
|
|
|
Remove the core dump from the report after stack trace regeneration
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:73
|
|
|
60.
|
|
|
Override report's ExecutablePath
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:79
|
