An Ubuntu problem-report window can collect much more than the error message you saw. Decide what diagnostic material may leave the computer before approving submission, especially when the affected application was handling customer documents or signed-in work accounts.

Inspect the proposed payload

Ubuntu documents a Show Details view in Apport for reviewing collected information. Its reports can include logs, stack traces and core dumps; these may contain private information. Package-specific hooks can collect additional diagnostics, so do not assume every application's report has the same contents.

Read the visible fields and attachment descriptions. Separate ordinary context, such as the Ubuntu and package version, from filenames, environment details, document contents or memory data that require a different disclosure decision. An encoded or compressed attachment is not evidence that it contains no private material.

For a workplace machine, use the organisation's agreed support process when you cannot meaningfully assess a dump. Keep the report local while that decision is unresolved. Avoid attaching the entire report to an unrelated public discussion simply because it has a technical-looking filename.

Prepare a useful minimal explanation

Write a short reproduction using a harmless sample where possible. For example, describe opening a blank test document and selecting the command that triggers the failure, while keeping the original customer document separate. Include whether the harmless sample reproduces the problem; do not claim it does if only the private original fails.

Ubuntu's documentation distinguishes inspection from submission: leaving the Send an error report choice enabled permits upload in the described dialog. It also describes apport-collect as collecting package information and uploading it to an existing Launchpad bug. Do not treat that command as a local-only preview when a support reply suggests it.

Before any approved upload, confirm the intended report destination and review the actual submission choices. Record whether the report remained local or was submitted so the recipient knows what evidence is available.

Preserve the original observation separately from the diagnostic payload. A reviewed, relevant report supports investigation; it does not establish a cause merely because a large amount of data was collected.

Sources: Ubuntu documentation.