238 lines
6.1 KiB
HTML
238 lines
6.1 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of apport-cli</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>apport-cli</H1>
|
|
Section: User Commands (1)<BR>Updated: August 01, 2007<BR><A HREF="#index">Index</A>
|
|
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
|
|
|
<P>
|
|
<A NAME="lbAB"> </A>
|
|
<H2>NAME</H2>
|
|
|
|
<P>
|
|
apport-cli, apport-gtk, apport-kde - Apport user interfaces for reporting problems
|
|
<P>
|
|
<A NAME="lbAC"> </A>
|
|
<H2>SYNOPSIS</H2>
|
|
|
|
<P>
|
|
<B>apport-cli</B>
|
|
|
|
<P>
|
|
<B>apport-cli </B>
|
|
|
|
[ <B>--save </B><I>file</I> ]
|
|
<I>symptom </I>|<I> pid </I>|<I> package </I>|<I> program path </I>|<I> .apport/.crash file</I>
|
|
|
|
<P>
|
|
<B>apport-cli -f</B>
|
|
|
|
<P>
|
|
<B>apport-cli -f -p</B>
|
|
|
|
<I>package</I>
|
|
|
|
<B>-P</B>
|
|
|
|
<I>pid</I>
|
|
|
|
<P>
|
|
<B>apport-cli -u</B>
|
|
|
|
<I>report-number</I>
|
|
|
|
<P>
|
|
Same options/arguments for
|
|
<B>apport-gtk</B>
|
|
|
|
and
|
|
<B>apport-kde</B>.
|
|
|
|
<P>
|
|
<A NAME="lbAD"> </A>
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
<P>
|
|
<B>apport </B>
|
|
|
|
automatically collects data from crashed processes and compiles a problem
|
|
report in
|
|
<I>/var/crash/</I>. This is a command line frontend for reporting
|
|
|
|
those crashes to the developers. It can also be used to report bugs
|
|
about packages or running processes.
|
|
<P>
|
|
If symptom scripts are available, it can also be given the name of a symptom,
|
|
or be called with just
|
|
<B>-f</B>
|
|
|
|
to display a list of known symptoms.
|
|
<P>
|
|
When being called without any options, it processes the pending crash reports
|
|
and offers to report them one by one. You can also display the entire report to
|
|
see what is sent to the software developers.
|
|
<P>
|
|
When being called with exactly one argument and no option,
|
|
<B>apport-cli</B>
|
|
|
|
uses some heuristics to find out "what you mean" and reports a bug against the
|
|
given symptom name, package name, program path, or PID. If the argument is a
|
|
<B>.crash </B>
|
|
|
|
or
|
|
<B>.apport</B>
|
|
|
|
file, it uploads the stored problem report to the bug tracking system.
|
|
<P>
|
|
For desktop systems with a graphical user interface, you should
|
|
consider installing the GTK or KDE user interface (apport-gtk or
|
|
apport-kde). They accept the very same options and arguments.
|
|
<B>apport-cli</B>
|
|
|
|
is mainly intended to be used on servers.
|
|
<P>
|
|
<A NAME="lbAE"> </A>
|
|
<H2>OPTIONS</H2>
|
|
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="1"><B>-f, --file-bug</B>
|
|
|
|
<DD>
|
|
Report a (non-crash) problem. If neither
|
|
<B>--package</B>,
|
|
|
|
<B>--symptom</B>,
|
|
|
|
or
|
|
<B>--pid</B>
|
|
|
|
are specified, then it displays a list of available symptoms. If none are
|
|
available, it aborts with an error.
|
|
<P>
|
|
This will automatically attach information about your operating system
|
|
and the package version etc. to the bug report, so that the developers
|
|
have some important context.
|
|
<P>
|
|
<DT id="2"><B>-s </B><I>symptom</I>, <B>--symptom</B>=<I>symptom</I>
|
|
|
|
<DD>
|
|
When being used in
|
|
<B>--file-bug</B>
|
|
|
|
mode, specify the symptom to report the problem about.
|
|
<P>
|
|
<DT id="3"><B>-p </B><I>package</I>, <B>--package</B>=<I>package</I>
|
|
|
|
<DD>
|
|
When being used in
|
|
<B>--file-bug</B>
|
|
|
|
mode, specify the package to report the problem against.
|
|
<P>
|
|
<DT id="4"><B>-P </B><I>pid</I>, <B>--pid</B>=<I>pid</I>
|
|
|
|
<DD>
|
|
When being used in
|
|
<B>--file-bug</B>
|
|
|
|
mode, specify the PID (process ID) of a running program to report the
|
|
problem against. This can be determined with e. g.
|
|
<B>ps -ux</B>.
|
|
|
|
<P>
|
|
<DT id="5"><B>-c </B><I>report</I>, <B>--crash-file</B>=<I>report</I>
|
|
|
|
<DD>
|
|
Upload a previously processed stored report in an arbitrary file location.
|
|
This is useful for copying a crash report to a machine with internet
|
|
connection and reporting it from there. Files must end in
|
|
<B>.crash</B>
|
|
|
|
or
|
|
<B>.apport</B>.
|
|
|
|
<P>
|
|
<DT id="6"><B>-u </B><I>report-number</I>, <B>--update-report </B><I>report-number</I>
|
|
|
|
<DD>
|
|
Run apport information collection on an already existing problem report. The
|
|
affected package is taken from the report by default, but you can explicitly
|
|
specify one with --package to collect information for a different package
|
|
(this is useful if the report is assigned to the wrong package).
|
|
<P>
|
|
<DT id="7"><B>--save </B><I>filename</I>
|
|
|
|
<DD>
|
|
In --file-bug mode, save the collected information into a file instead of
|
|
reporting it. This file can then be reported with --crash-file later on.
|
|
<P>
|
|
<DT id="8"><B>-w, --window</B>
|
|
|
|
<DD>
|
|
Point and click at the application window against which you wish to report
|
|
the bug. Apport will automatically find the package name and generate a report
|
|
for you. This option can be specially useful in situations when you do not know
|
|
the name of the package, or if the application window has stopped responding
|
|
and you cannot report the problem from the "Help" menu of the application.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAF"> </A>
|
|
<H2>ENVIRONMENT</H2>
|
|
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="9"><B>APPORT_IGNORE_OBSOLETE_PACKAGES</B>
|
|
|
|
<DD>
|
|
Apport refuses to create bug reports if the package or any dependency is not
|
|
current. If this environment variable is set, this check is waived. Experts who
|
|
will thoroughly check the situation before filing a bug report can define this
|
|
in their
|
|
<B>~/.bashrc</B>
|
|
|
|
or temporarily when calling the apport frontend (-cli, -gtk, or -kde).
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAG"> </A>
|
|
<H2>FILES</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="10"><B>/usr/share/apport/symptoms/*.py</B>
|
|
|
|
<DD>
|
|
Symptom scripts. These ask a set of interactive questions to determine the
|
|
package which is responsible for a particular problem. (For some problems like
|
|
sound or storage device related bugs there are many places where things can go
|
|
wrong, and it's not immediately obvious for a bug reporter where the problem is.)
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAH"> </A>
|
|
<H2>AUTHOR</H2>
|
|
|
|
<B>apport</B>
|
|
|
|
and the accompanying tools are developed by Martin Pitt
|
|
<<A HREF="mailto:martin.pitt@ubuntu.com">martin.pitt@ubuntu.com</A>>.
|
|
<P>
|
|
|
|
<HR>
|
|
<A NAME="index"> </A><H2>Index</H2>
|
|
<DL>
|
|
<DT id="11"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="12"><A HREF="#lbAC">SYNOPSIS</A><DD>
|
|
<DT id="13"><A HREF="#lbAD">DESCRIPTION</A><DD>
|
|
<DT id="14"><A HREF="#lbAE">OPTIONS</A><DD>
|
|
<DT id="15"><A HREF="#lbAF">ENVIRONMENT</A><DD>
|
|
<DT id="16"><A HREF="#lbAG">FILES</A><DD>
|
|
<DT id="17"><A HREF="#lbAH">AUTHOR</A><DD>
|
|
</DL>
|
|
<HR>
|
|
This document was created by
|
|
<A HREF="/cgi-bin/man/man2html">man2html</A>,
|
|
using the manual pages.<BR>
|
|
Time: 00:05:06 GMT, March 31, 2021
|
|
</BODY>
|
|
</HTML>
|