{
    "content": [
        {
            "type": "text",
            "text": "# apport-cli(1) (man)\n\n**Summary:** apport-cli, apport-gtk, apport-kde - Apport user interfaces for reporting problems\n\n## Flags\n\n| Flag | Long | Arg | Description |\n|------|------|-----|-------------|\n| -f | --file-bug | — | Report a (non-crash) problem. If neither --package, --symptom, or --pid are specified, then it displays a list of availa |\n| -s | --symptom | — | When being used in --file-bug mode, specify the symptom to report the problem about. |\n| -p | --package | — | When being used in --file-bug mode, specify the package to report the problem against. |\n| -P | --pid | — | When being used in --file-bug mode, specify the PID (process ID) of a running program to report the problem against. Thi |\n| -c | --crash-file | — | Upload a previously processed stored report in an arbitrary file location. This is useful for copying a crash report to  |\n| -u | --update-report | — | Run apport information collection on an already existing problem report. The affected package is taken from the report b |\n| -w | --window | — | Point and click at the application window against which you wish to report the bug. Apport will automatically find the p |\n\n## Section Outline\n\n- **NAME** (3 lines)\n- **SYNOPSIS** (1 lines) — 2 subsections\n  - apport-cli (2 lines)\n  - apport-cli -f (7 lines)\n- **DESCRIPTION** (21 lines)\n- **OPTIONS** (1 lines) — 7 subsections\n  - -f, --file-bug (8 lines)\n  - -s --symptom (3 lines)\n  - -p --package (3 lines)\n  - -P --pid (4 lines)\n  - -c --crash-file (5 lines)\n  - -u --update-report (11 lines)\n  - -w, --window (10 lines)\n- **ENVIRONMENT** (7 lines)\n- **FILES** (7 lines)\n- **AUTHOR** (5 lines)\n\n## Full Content\n\n### NAME\n\napport-cli, apport-gtk, apport-kde - Apport user interfaces for reporting problems\n\n### SYNOPSIS\n\n#### apport-cli\n\napport-cli [ --save file ] symptom | pid | package | program path | .apport/.crash file\n\n#### apport-cli -f\n\napport-cli -f -p package -P pid\n\napport-cli -u report-number\n\nSame options/arguments for apport-gtk and apport-kde.\n\n### DESCRIPTION\n\napport  automatically  collects  data from crashed processes and compiles a problem report in\n/var/crash/. This is a command line frontend for reporting those crashes to  the  developers.\nIt can also be used to report bugs about packages or running processes.\n\nIf  symptom  scripts  are available, it can also be given the name of a symptom, or be called\nwith just -f to display a list of known symptoms.\n\nWhen being called without any options, it processes the pending crash reports and  offers  to\nreport  them  one  by  one. You can also display the entire report to see what is sent to the\nsoftware developers.\n\nWhen being called with exactly one argument and no option, apport-cli uses some heuristics to\nfind out \"what you mean\" and reports a bug against the given symptom name, package name, pro‐\ngram path, or PID. If the argument is a .crash or .apport file, it uploads the stored problem\nreport to the bug tracking system.\n\nFor  desktop  systems with a graphical user interface, you should consider installing the GTK\nor KDE user interface (apport-gtk or apport-kde). They accept the very same options and argu‐\nments.  apport-cli is mainly intended to be used on servers.\n\n### OPTIONS\n\n#### -f, --file-bug\n\nReport a (non-crash) problem. If neither --package, --symptom, or --pid are specified,\nthen it displays a list of available symptoms. If none are available, it  aborts  with\nan error.\n\nThis will automatically attach information about your operating system and the package\nversion etc. to the bug report, so that the developers have some important context.\n\n#### -s --symptom\n\nWhen being used in --file-bug mode, specify the symptom to report the problem about.\n\n#### -p --package\n\nWhen being used in --file-bug mode, specify the package to report the problem against.\n\n#### -P --pid\n\nWhen being used in --file-bug mode, specify the PID (process ID) of a running  program\nto report the problem against. This can be determined with e. g.  ps -ux.\n\n#### -c --crash-file\n\nUpload  a  previously  processed stored report in an arbitrary file location.  This is\nuseful for copying a crash report to a machine with internet connection and  reporting\nit from there. Files must end in .crash or .apport.\n\n#### -u --update-report\n\nRun  apport information collection on an already existing problem report. The affected\npackage is taken from the report by default, but you can explicitly specify  one  with\n--package to collect information for a different package (this is useful if the report\nis assigned to the wrong package).\n\n\n--save filename\nIn --file-bug mode, save the collected information into a file  instead  of  reporting\nit. This file can then be reported with --crash-file later on.\n\n#### -w, --window\n\nPoint  and  click  at the application window against which you wish to report the bug.\nApport will automatically find the package name and generate a report  for  you.  This\noption  can  be  specially  useful  in situations when you do not know the name of the\npackage, or if the application window has stopped responding and you cannot report the\nproblem from the \"Help\" menu of the application.\n\nThis  option is not supported on Wayland. Users running Wayland should use another op‐\ntion such as -P to specify the application.\n\n### ENVIRONMENT\n\nAPPORTIGNOREOBSOLETEPACKAGES\nApport refuses to create bug reports if the package or any dependency is not  current.\nIf this environment variable is set, this check is waived. Experts who will thoroughly\ncheck the situation before filing a bug report can define this in their  ~/.bashrc  or\ntemporarily when calling the apport frontend (-cli, -gtk, or -kde).\n\n### FILES\n\n/usr/share/apport/symptoms/*.py\nSymptom  scripts.  These  ask  a set of interactive questions to determine the package\nwhich is responsible for a particular problem. (For some problems like sound or  stor‐\nage  device related bugs there are many places where things can go wrong, and it's not\nimmediately obvious for a bug reporter where the problem is.)\n\n### AUTHOR\n\napport and the accompanying tools are developed by Martin Pitt <martin.pitt@ubuntu.com>.\n\n\n\nMartin Pitt                                August 01, 2007                             apport-cli(1)\n\n"
        }
    ],
    "structuredContent": {
        "command": "apport-cli",
        "section": "1",
        "mode": "man",
        "summary": "apport-cli, apport-gtk, apport-kde - Apport user interfaces for reporting problems",
        "synopsis": "",
        "flags": [
            {
                "flag": "-f",
                "long": "--file-bug",
                "arg": null,
                "description": "Report a (non-crash) problem. If neither --package, --symptom, or --pid are specified, then it displays a list of available symptoms. If none are available, it aborts with an error. This will automatically attach information about your operating system and the package version etc. to the bug report, so that the developers have some important context."
            },
            {
                "flag": "-s",
                "long": "--symptom",
                "arg": null,
                "description": "When being used in --file-bug mode, specify the symptom to report the problem about."
            },
            {
                "flag": "-p",
                "long": "--package",
                "arg": null,
                "description": "When being used in --file-bug mode, specify the package to report the problem against."
            },
            {
                "flag": "-P",
                "long": "--pid",
                "arg": null,
                "description": "When being used in --file-bug mode, specify the PID (process ID) of a running program to report the problem against. This can be determined with e. g. ps -ux."
            },
            {
                "flag": "-c",
                "long": "--crash-file",
                "arg": null,
                "description": "Upload a previously processed stored report in an arbitrary file location. This is useful for copying a crash report to a machine with internet connection and reporting it from there. Files must end in .crash or .apport."
            },
            {
                "flag": "-u",
                "long": "--update-report",
                "arg": null,
                "description": "Run apport information collection on an already existing problem report. The affected package is taken from the report by default, but you can explicitly specify one with --package to collect information for a different package (this is useful if the report is assigned to the wrong package). --save filename In --file-bug mode, save the collected information into a file instead of reporting it. This file can then be reported with --crash-file later on."
            },
            {
                "flag": "-w",
                "long": "--window",
                "arg": null,
                "description": "Point and click at the application window against which you wish to report the bug. Apport will automatically find the package name and generate a report for you. This option can be specially useful in situations when you do not know the name of the package, or if the application window has stopped responding and you cannot report the problem from the \"Help\" menu of the application. This option is not supported on Wayland. Users running Wayland should use another op‐ tion such as -P to specify the application."
            }
        ],
        "examples": [],
        "see_also": [],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 1,
                "subsections": [
                    {
                        "name": "apport-cli",
                        "lines": 2
                    },
                    {
                        "name": "apport-cli -f",
                        "lines": 7
                    }
                ]
            },
            {
                "name": "DESCRIPTION",
                "lines": 21,
                "subsections": []
            },
            {
                "name": "OPTIONS",
                "lines": 1,
                "subsections": [
                    {
                        "name": "-f, --file-bug",
                        "lines": 8,
                        "flag": "-f",
                        "long": "--file-bug"
                    },
                    {
                        "name": "-s --symptom",
                        "lines": 3,
                        "flag": "-s",
                        "long": "--symptom"
                    },
                    {
                        "name": "-p --package",
                        "lines": 3,
                        "flag": "-p",
                        "long": "--package"
                    },
                    {
                        "name": "-P --pid",
                        "lines": 4,
                        "flag": "-P",
                        "long": "--pid"
                    },
                    {
                        "name": "-c --crash-file",
                        "lines": 5,
                        "flag": "-c",
                        "long": "--crash-file"
                    },
                    {
                        "name": "-u --update-report",
                        "lines": 11,
                        "flag": "-u",
                        "long": "--update-report"
                    },
                    {
                        "name": "-w, --window",
                        "lines": 10,
                        "flag": "-w",
                        "long": "--window"
                    }
                ]
            },
            {
                "name": "ENVIRONMENT",
                "lines": 7,
                "subsections": []
            },
            {
                "name": "FILES",
                "lines": 7,
                "subsections": []
            },
            {
                "name": "AUTHOR",
                "lines": 5,
                "subsections": []
            }
        ]
    }
}