Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #957
Difficulty: Medium
Metamorphic code is code that when run outputs a logically equivalent version of its own code under some interpretation.
True or False?
Linux & Unix Commands - Search Man Pages

ubuntu-bug(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

dupdp-admin(1)						      General Commands Manual						    dupdp-admin(1)

NAME
dupdb-admin - Manage the duplicate database for apport-retrace. SYNOPSIS
dupdb-admin -f dbpath status dupdb-admin -f dbpath dump dupdb-admin -f dbpath changeid oldid newid DESCRIPTION
apport-retrace(1) has the capability of checking for duplicate bugs (amonst other things). It uses an SQLite database for keeping track of master bugs. dupdb-admin is a small tool to manage that database. The central concept in that database is a "crash signature", a string that uniquely identifies a particular crash. It is built from the executable path name, the signal number or exception name, and the topmost functions of the stack trace. The database maps crash signatures to the 'master' crash id and thus can close duplicate crash reports with a reference to that master ID. It also tracks the status of crashes (open/fixed in a particular version) to be able to identify regressions. MODES
status Print general status of the duplicate db. For now, it only shows the time when the database was "consolidated" last, i. e. when the bug states (open/fixed) in the SQLite database where updated to the actual states in the bug tracking system. dump Print a list of all database entries. changeid Change the associated crash ID for a particular crash. OPTIONS
-f path, --database-file=path Instead of processing the new crash reports in /var/crash/, report a particular report in an arbitrary file location. This is use- ful for copying a crash report to a machine with internet connection and reporting it from there. This defaults to ~./apport_dupli- cates.db. AUTHOR
apport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>. Martin Pitt August 01, 2007 dupdp-admin(1)

Featured Tech Videos