|
|
97.
|
|
|
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
|
|
|
98.
|
|
|
This will remove some large items from the report. These are very useful for developers to debug the problem, but might be too big for you to upload if you have a slow internet connection.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../gtk/apport-gtk.ui.h:10
|
|
|
99.
|
|
|
_Ignore future crashes of this program version
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../gtk/apport-gtk.ui.h:16
|
|
|
100.
|
|
|
_Report Problem...
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../gtk/apport-gtk.ui.h:14
|
|
|
101.
|
|
|
_Send Report
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../gtk/apport-gtk.ui.h:2
|
|
|
102.
|
|
|
%prog [options] <apport problem report | crash ID>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:37
|
|
|
103.
|
|
|
Do not put the new traces into the report, but write them to stdout.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:48
|
|
|
104.
|
|
|
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
|
|
|
105.
|
|
|
Write modified report to given file instead of changing the original report
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:64
|
|
|
106.
|
|
|
Remove the core dump from the report after stack trace regeneration
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:73
|
