Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

apport-collect(1) [linux man page]

apport-bug(1)						      General Commands Manual						     apport-bug(1)

NAME
apport-bug, apport-collect - file a bug report using Apport, or update an existing report SYNOPSIS
apport-bug apport-bug symptom | pid | package | program path | .apport/.crash file apport-collect report-number DESCRIPTION
apport-bug reports problems to your distribution's bug tracking system, using Apport to collect a lot of local information about your sys- tem to help the developers to fix the problem and avoid unnecessary question/answer turnarounds. You should always start with running apport-bug without arguments, which will present a list of known symptoms. This will generate the most useful bug reports. 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 apport-bug, e. g.: apport-bug firefox apport-bug /usr/bin/unzip 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: $ pidof gnome-terminal 5139 $ apport-bug 5139 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 apport-bug linux to report a bug against the currently running kernel. Finally, you can use this program to report a previously stored crash or bug report: apport-bug /var/crash/_bin_bash.1000.crash apport-bug /tmp/apport.firefox.332G9t.apport Bug reports can be written to a file by using the --save option or by using apport-cli. apport-bug detects whether KDE or Gnome is running and calls apport-gtk or apport-kde accordingly. If neither is available, or the session does not run under X11, it calls apport-cli for a command-line client. UPDATING EXISTING REPORTS
apport-collect 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. OPTIONS
Please see the apport-cli(1) manpage for possible options. ENVIRONMENT
APPORT_IGNORE_OBSOLETE_PACKAGES 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 ~/.bashrc or temporarily on the command line when calling apport-bug. SEE ALSO
apport-cli(1) AUTHOR
apport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>. Martin Pitt September 08, 2009 apport-bug(1)

Check Out this Related Man Page

MASS-BUG(1)                                                                                                                            MASS-BUG(1)

NAME
mass-bug - mass-file a bug report against a list of packages SYNOPSIS
mass-bug [options] --subject="bug subject" template package-list DESCRIPTION
mass-bug assists in filing a mass bug report in the Debian BTS on a set of packages. For each package in the package-list file (which should list one package per line together with an optional version number separated from the package name by an underscore), it fills out the template, adds BTS pseudo-headers, and either displays or sends the bug report. Warning: Some care has been taken to avoid unpleasant and common mistakes, but this is still a power tool that can generate massive amounts of bug report mails. Use it with care, and read the documentation in the Developer's Reference about mass filing of bug reports first. TEMPLATE
The template file is the body of the message that will be sent for each bug report, excluding the BTS pseudo-headers. In the template, #PACKAGE# is replaced with the name of the package. If a version was specified for the package, #VERSION# will be replaced by that version. The components of the version number may be specified using #EPOCH#, #UPSTREAM_VERSION# and #REVISION#. #EPOCH# includes the trailing colon and #REVISION# the leading dash so that #EPOCH#UPSTREAM_VERSION##REVISION# is always the same as #VERSION#. Note that text in the template will be automatically word-wrapped to 70 columns, up to the start of a signature (indicated by '--' at the start of a line on its own). This is another reason to avoid including BTS pseudo-headers in your template. OPTIONS
mass-bug examines the devscripts configuration files as described below. Command line options override the configuration file settings, though. --severity=(wishlist|minor|normal|important|serious|grave|critical) Specify the severity with which bugs should be filed. Default is normal. --display Fill out the templates for each package and display them all for verification. This is the default behavior. --send Actually send the bug reports. --subject="bug subject" Specify the subject of the bug report. The subject will be automatically prefixed with the name of the package that the bug is filed against. --tags Set the BTS pseudo-header for tags. --user Set the BTS pseudo-header for a usertags' user. --usertags Set the BTS pseudo-header for usertags. --source Specify that package names refer to source packages rather than binary packages. --sendmail=SENDMAILCMD Specify the sendmail command. The command will be split on white space and will not be passed to a shell. Default is /usr/sbin/sendmail. --no-wrap Do not wrap the template to lines of 70 characters. --no-conf, --noconf Do not read any configuration files. This can only be used as the first option given on the command-line. --help Provide a usage message. --version Display version information. ENVIRONMENT
DEBEMAIL and EMAIL can be set in the environment to control the email address that the bugs are sent from. CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables. Command line options can be used to override configuration file settings. Environment variable settings are ignored for this purpose. The currently recognised variables are: BTS_SENDMAIL_COMMAND If this is set, specifies a sendmail command to use instead of /usr/sbin/sendmail. Same as the --sendmail command line option. COPYRIGHT
This program is Copyright (C) 2006 by Joey Hess <joeyh@debian.org>. It is licensed under the terms of the GPL, either version 2 of the License, or (at your option) any later version. AUTHOR
Joey Hess <joeyh@debian.org> Debian Utilities 2013-12-23 MASS-BUG(1)
Man Page