Skip Quicknav * About Debian * Getting Debian * Support * Developers' Corner Debian bug tracking system / Debian BTS - reporting bugs How to report a bug in Debian using reportbug We strongly recommend that you report bugs in Debian using the reportbug program. To install and start it, simply run: # apt-get install reportbug $ reportbug It will guide you through the bug reporting process step by step. If you have questions that the interactive prompts of reportbug do not resolve, you can refer to the rest of the documentation below or ask the Debian user mailing list. How to report a bug in Debian using email (and advanced usage of reportbug) Important things to note before sending your bug report What package does your bug report belong to? You need to know what package your bug report should be filed against. See this example for information on how to find this information. (You will use this information to see if your bug report has been filed already.) If you are unable to determine which package your bug report should be filed against, please send e-mail to the Debian user mailing list asking for advice. If your problem doesn't relate just to one package but some general Debian service, there are several pseudo-packages or even mailing lists that you can use to relay your message to us instead. Has your bug report been filed already? You should check to see if your bug report has already been filed before submitting it. You can see which bugs have been filed in a specific package using the package option of the bug search form. If there is an existing bug report #, you should submit your comments by sending e-mail to instead of reporting a new bug. Send multiple reports for multiple bugs Please don't report multiple unrelated bugs — especially ones in different packages — in a single bug report. Don't file bugs upstream If you file a bug in Debian, don't send a copy to the upstream software maintainers yourself, as it is possible that the bug exists only in Debian. If necessary, the maintainer of the package will forward the bug upstream. Sending the bug report via e-mail You can report bugs in Debian by sending an e-mail to with a special format described below. reportbug (see above) will properly format the e-mails for you; please use it! Headers Like any e-mail you should include a clear, descriptive Subject line in your main mail header. The subject you give will be used as the initial bug title in the tracking system, so please try to make it informative! If you'd like to send a copy of your bug report to additional recipients (such as mailing lists), you shouldn't use the usual e-mail headers, but a different method, described below. Pseudo-headers The first part of the bug report are the pseudo-headers which contain information about what package and version your bug report applies to. The first line of the message body has to include a pseudo-header. It should say: Package: Replace with the name of the package which has the bug. The second line of the message should say: Version: Replace with the version of the package. Please don't include any text here other than the version itself, as the bug tracking system relies on this field to work out which releases are affected by the bug. You need to supply a correct Package line in the pseudo-header in order for the bug tracking system to deliver the message to the package's maintainer. See this example for information on how to find this information. For other valid pseudo-headers, see Additional pseudo-headers The body of the report Please include in your report: * The exact and complete text of any error messages printed or logged. This is very important! * Exactly what you typed or did to demonstrate the problem. * A description of the incorrect behavior: exactly what behavior you were expecting, and what you observed. A transcript of an example session is a good way of showing this. * A suggested fix, or even a patch, if you have one. * Details of the configuration of the program with the problem. Include the complete text of its configuration files. * The versions of any packages on which the buggy package depends. * What kernel version you're using (type uname -a), your shared C library (type ls -l /lib/ or dpkg -s libc6 | grep ^Version), and any other details about your Debian system, if it seems appropriate. For example, if you had a problem with a Perl script, you would want to provide the version of the `perl' binary (type perl -v or dpkg -s perl | grep ^Version:). * Appropriate details of the hardware in your system. If you're reporting a problem with a device driver please list all the hardware in your system, as problems are often caused by IRQ and I/O address conflicts. * If you have reportbug installed the output of reportbug -q --template -T none -s none -S normal -b --list-cc none -q will also be useful, as it contains the output of maintainer specific scripts and version information. Include any detail that seems relevant — you are in very little danger of making your report too long by including too much information. If they are small, please include in your report any files you were using to reproduce the problem. (If they are large, consider making them available on a publicly available website if possible.) For more advice on how to help the developers solve your problem, please read How to Report Bugs Effectively. An Example Bug Report A bug report with header and pseudo-header looks something like this: To: From: Subject: Hello says `goodbye' Package: hello Version: 1.3-16 When I invoke `hello' without arguments from an ordinary shell prompt it prints `goodbye', rather than the expected `hello, world'. Here is a transcript: $ hello goodbye $ /usr/bin/hello goodbye $ I suggest that the ouHTTP/1.1 403 Forbidden Connection: close Content-Length: 1807 Content-Type: text/html; charset=UTF-8 Restricted Content

Access to this website is restricted by NUS

Computer Centre is putting additional security control to protect your computer as well as NUS systems from cyber security threats. We detected that the website you have attempted to visit may contain harmful content and could potentially damage your computer or other NUS systems.