211 lines
4.8 KiB
HTML
211 lines
4.8 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of apport-bug</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>apport-bug</H1>
|
|
Section: User Commands (1)<BR>Updated: September 08, 2009<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-bug, apport-collect - file a bug report using Apport, or update an existing report
|
|
<P>
|
|
<A NAME="lbAC"> </A>
|
|
<H2>SYNOPSIS</H2>
|
|
|
|
<P>
|
|
<B>apport-bug</B>
|
|
|
|
<P>
|
|
<B>apport-bug</B>
|
|
|
|
<I>symptom </I>|<I> pid </I>|<I> package </I>|<I> program path </I>|<I> .apport/.crash file</I>
|
|
|
|
<P>
|
|
<B>apport-collect</B>
|
|
|
|
<I>report-number</I>
|
|
|
|
<P>
|
|
<A NAME="lbAD"> </A>
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
<P>
|
|
<B>apport-bug</B>
|
|
|
|
reports problems to your distribution's bug tracking system,
|
|
using Apport to collect a lot of local information about your system to help
|
|
the developers to fix the problem and avoid unnecessary question/answer
|
|
turnarounds.
|
|
<P>
|
|
You should always start with running
|
|
<B>apport-bug</B>
|
|
|
|
without arguments, which will present a list of known symptoms. This will
|
|
generate the most useful bug reports.
|
|
<P>
|
|
If there is no matching symptom, you need to determine the affected program or
|
|
package yourself. You can provide a package name or program name to
|
|
<B>apport-bug</B>,
|
|
|
|
e. g.:
|
|
<P>
|
|
<DL COMPACT><DT id="1"><DD>
|
|
<PRE>
|
|
apport-bug firefox
|
|
apport-bug /usr/bin/unzip
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
In order to add more information to the bug report that could
|
|
help the developers to fix the problem, you can also specify a process
|
|
ID instead:
|
|
<P>
|
|
<DL COMPACT><DT id="2"><DD>
|
|
<PRE>
|
|
$ pidof gnome-terminal
|
|
5139
|
|
$ apport-bug 5139
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
As a special case, to report a bug against the Linux kernel, you do not need to
|
|
use the full package name (such as linux-image-2.6.28-4-generic); you can just use
|
|
<P>
|
|
<DL COMPACT><DT id="3"><DD>
|
|
<PRE>
|
|
apport-bug linux
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
to report a bug against the currently running kernel.
|
|
<P>
|
|
Finally, you can use this program to report a previously stored crash or bug report:
|
|
<P>
|
|
<DL COMPACT><DT id="4"><DD>
|
|
<PRE>
|
|
apport-bug /var/crash/_bin_bash.1000.crash
|
|
apport-bug /tmp/apport.firefox.332G9t.apport
|
|
</PRE>
|
|
|
|
</DL>
|
|
|
|
<P>
|
|
Bug reports can be written to a file by using the
|
|
<B>--save</B>
|
|
|
|
option or by using
|
|
<B>apport-cli</B>.
|
|
|
|
<P>
|
|
<B>apport-bug</B>
|
|
|
|
detects whether KDE or Gnome is running and calls
|
|
<B>apport-gtk</B>
|
|
|
|
or
|
|
<B>apport-kde</B>
|
|
|
|
accordingly. If neither is available, or the session does not run
|
|
under X11, it calls
|
|
<B>apport-cli</B>
|
|
|
|
for a command-line client.
|
|
<P>
|
|
<A NAME="lbAE"> </A>
|
|
<H2>UPDATING EXISTING REPORTS</H2>
|
|
|
|
<P>
|
|
<B>apport-collect</B>
|
|
|
|
collects the same information as apport-bug, but adds it to an already
|
|
reported problem you have submitted. This is useful if the report was
|
|
not originally filed through Apport, and the developers ask you to attach
|
|
information from your system.
|
|
<P>
|
|
<A NAME="lbAF"> </A>
|
|
<H2>OPTIONS</H2>
|
|
|
|
Please see the
|
|
<B><A HREF="/cgi-bin/man/man2html?1+apport-cli">apport-cli</A>(1)</B>
|
|
|
|
manpage for possible options.
|
|
<P>
|
|
<A NAME="lbAG"> </A>
|
|
<H2>ENVIRONMENT</H2>
|
|
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="5"><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 on the command line when calling
|
|
<B>apport-bug</B>.
|
|
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAH"> </A>
|
|
<H2>FILES</H2>
|
|
|
|
apport crash files are written in to
|
|
<B>/var/crash</B>
|
|
|
|
by default, named uniquely per binary name and user id. They are not deleted
|
|
after being sent to the bug tracker (but from cron when they get older than 7
|
|
days). You can extract the core file (if any) and other information using
|
|
<B>apport-unpack.</B>
|
|
|
|
<P>
|
|
<A NAME="lbAI"> </A>
|
|
<H2>SEE ALSO</H2>
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+apport-cli">apport-cli</A></B>(1),
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+apport-unpack">apport-unpack</A></B>(1)
|
|
|
|
<P>
|
|
<A NAME="lbAJ"> </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="6"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="7"><A HREF="#lbAC">SYNOPSIS</A><DD>
|
|
<DT id="8"><A HREF="#lbAD">DESCRIPTION</A><DD>
|
|
<DT id="9"><A HREF="#lbAE">UPDATING EXISTING REPORTS</A><DD>
|
|
<DT id="10"><A HREF="#lbAF">OPTIONS</A><DD>
|
|
<DT id="11"><A HREF="#lbAG">ENVIRONMENT</A><DD>
|
|
<DT id="12"><A HREF="#lbAH">FILES</A><DD>
|
|
<DT id="13"><A HREF="#lbAI">SEE ALSO</A><DD>
|
|
<DT id="14"><A HREF="#lbAJ">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>
|