How to Submit a Debian Bug Report
How to Submit a Debian Bug Report
Please carefully read the following information about how to write a
bug report for Debian Linux. Following these guidelines will greatly
increase the chances that someone will have enough information to
correct your problem.
Please read the Linux FAQ before sending in a bug report. The Linux
FAQ is located in /usr/doc if you installed `doc.deb' on your Debian
system. The Linux FAQ is also available in
nic.funet.fi (128.214.6.100) /pub/OS/Linux/doc
tsx-11.mit.edu (18.172.1.2) /pub/linux/docs
sunsite.unc.edu (152.2.22.81) /pub/Linux/docs
Please read appropriate HOWTO documents, info pages, manual pages, or
other miscellaneous documentation. HOWTO and miscellaneous documents
are located in /usr/doc if you installed `doc.deb' on your Debian
system. They are also available in
nic.funet.fi (128.214.6.100) /pub/OS/Linux/doc/HOWTO
tsx-11.mit.edu (18.172.1.2) /pub/linux/docs/HOWTO
sunsite.unc.edu (152.2.22.81) /pub/Linux/docs/HOWTO
Please read the Debian PROBLEMS file before sending in a bug report.
The PROBLEMS file describes known bugs in the current version of Debian
and any known fixes. Please do not report problems listed in this file
unless you have a fix for them. This is not yet written, but will be
made available on sunsite.unc.edu in the future.
Please send the completed form, located below, to debian-bugs@pixar.com
or debian-user@pixar.com (the former is encouraged). For problems that
you are unable to understand or correct, use the debian-bugs address.
Information about interim solutions will be posted regularly to the
debian-announce@pixar.com list.
Please delete the text in brackets before sending it in.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- cut here -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Debian Bug Report (version 1.0)
DEBIAN VERSION:
[The version of Debian you are using. For example, `0.91']
----- Hardware ---------------------------------------------------------
PROCESSOR:
[The processor of your machine. For example, `Intel 386/33dx'. If you
have a math coprocessor, please include the type. Please also include
the name of the chip manufacturer.]
MEMORY:
[The amount of memory in your machine, with and without swap. For
example, `8 MB / 16 MB'.]
ARCHITECTURE:
[The architecture of your machine. For example, `EISA']
OTHER HARDWARE INFORMATION [optional]:
[Details of what hardware you're running on, if it seems appropriate.
For example, for a hard drive related problem you would want to
specify the type of your hard drive controller.]
----- System -----------------------------------------------------------
KERNEL VERSION:
[The output of "uname -a" on your machine.]
SHARED LIBRARY VERSION:
[The output of "ls -l /lib/lib.c.so.4".]
OTHER SYSTEM INFORMATION [optional]:
[Any other details of your Linux system, if it seems appropriate. For
example, if you had a problem with a Debian Perl script, you would want
to provide the version of the `perl' binary.]
----- Problem ----------------------------------------------------------
CONFIGURATION:
[The contents of any configuration files used by the program in question
and any related programs.]
PROGRAM:
[The name of the program which you are having problems with, where you
got it, and the version of the program. Many standard commands tell you
their version number if you give them a "--version" or "-V" option.]
DESCRIPTION OF INCORRECT BEHAVIOR:
[Exactly what behavior you were expecting, and exactly what behavior
you observed. A transcript of an example session is a good way of
showing this.]
ERROR MESSAGES:
[The *exact* and *complete* text of any error messages printed.]
SUGGESTED FIX [optional]:
[If you can suggest a fix for the problem, include a context diff here.
But don't delay sending in a bug report in the hope of finding a fix.]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- cut here -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
The "Debian Bug Report Form" is maintained by Daniel Quinlan. Thanks to
Ian Jackson for information provided in the Linux FAQ on reporting bugs.
--
Daniel Quinlan <quinlan@spectrum.cs.bucknell.edu>
Reply to: