|
|
74.
|
|
|
Path to file (Enter to cancel):
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-cli.py:384
|
|
|
76.
|
|
|
This is a directory.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-cli.py:392
|
|
|
81.
|
|
|
This occured during a previous suspend and prevented it from resuming properly.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../data/apportcheckresume.py:68
|
|
|
82.
|
|
|
This occured during a previous hibernate and prevented it from resuming properly.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../data/apportcheckresume.py:70
|
|
|
83.
|
|
|
The resume processing hung very near the end and will have appeared to have completed normally.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../data/apportcheckresume.py:88
|
|
|
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
|
|
|
106.
|
|
|
Remove the core dump from the report after stack trace regeneration
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:73
|
|
|
107.
|
|
|
Override report's CoreFile
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../bin/apport-retrace.py:76
|
