Skip to main content

Disable creating crash reports to send (Apport)

Apply Now
Works with any Linux distroWorks with any Linux distribution that can run bash scripts.
  • Linux onlyThis script improves your privacy on Linux
  • Multiple actionsThis page belongs to a category, containing some changes with similar goal.
  • Impact: Minimum

    System Functionality / Data Loss Risk: Low

    This action improves privacy with minimal impact when you run the recommended script.

  • Bash (Shell script)These changes use Linux system commands to update your settings.
  • 3 scripts
  • No subcategories
  • Sudo/root requiredThis script requires privilege access to do the system changes
  • Fully reversible

    You can fully restore this action (revert back to the original behavior) using this website.

    The restore/revert methods provided here can help you fix issues.

Overview​

Apport intercepts program crashes, collects debugging information about the crash and the operating system environment, and sends it to bug trackers in a standardized form 1. It also allows the user to report a bug about a package by collecting as much information about it as possible 1.

Disabling Apport prevents the UI which informs the user about the crash and instructs them on how to proceed because that dialog is part of Apport 2 3. Furthermore, Apport creates crash report files in the /var/crash directory, and having files in this directory causes an error message to appear every time Ubuntu boots 4.

Apport collects potentially sensitive data, such as core dumps, stack traces, and log files 2. It can contain passwords, credit card numbers, serial numbers, and other private information 2.

Bug reports are shared with the Ubuntu bug triaging team 2.

Apport is disabled by default in stable releases due to the sensitive data it collects 2.

Apport only uploads data if the package whoopsie is installed; otherwise it appears to be uploading but does not upload 3.

Safe for General Use
This script has Normal protection level option. This is recommended for all users to improve without any noticeable impact on the system functionality.
Sources
PrivacyLearn.com maintains strict sourcing standards for accuracy, integrity and up-to-date content. Our content relies on authoritative sources including vendor documentation, industry standards, and verified research. Learn more about our verification process and quality standards in our editorial standards page.

Apply Now​

Choose one of two ways to apply:

Download script​

Download and run the script directly
  • No app needed
  • Offline usage
  • Free
  • Open-source

Normal — Everyday Privacy (Enterprise-Grade)​

  • Recommended for all
  • Safe for daily use
  • No impact on system stability

Read more about Normal and other protection levels

Help

How to apply or restore "Disable creating crash reports to send (Apport)" using script​

  • ≈ 3 min to complete
  • Tools: Web Browser
  • Difficulty: Medium
  • ≈ 6 instructions
  1. 1

    Choose protection

    Choose one of the options with different impact levels:

    • Normal

      Some safe changes minimal system impact.

    • High

      Some potentially impactful changes with moderate system impact.
  2. 2

    Download

    Download the script file by clicking on the   Apply protection  button above.
    Use   Undo protection button above to restore changes.
  3. 3

    Keep the file

    If warned by your browser, keep the file.
  4. 4

    Open

    Open the downloaded file.
  5. 5

    Exit

    Once it's done, press any key to exit the window.
  6. 6

    Restart

    Restart your computer for all changes to take effect.

Apply with privacy.sexy​

Guided, automated application with safety checks
  • Recommended for most users
  • Includes safety checks
  • Shows the code
  • Free
  • Open-source
  • Popular
  • Offline/Online usage
Open privacy.sexy
Help

How to apply or restore "Disable creating crash reports to send (Apport)" using privacy.sexy​

  • ≈ 3 min to complete
  • Tools: privacy.sexy
  • Difficulty: Simple
  • ≈ 4 instructions
privacy.sexy is free and open-source application that lets securely apply this action easily with more advanced options.
  1. 1

    Open or download

    Open or download the desktop application
  2. 2

    Choose script

    1. Search for the category name: Disable creating crash reports to send (Apport)
    2. Check the category by clicking on the checkbox of the category.

    Applying Normal to limit the impact.

  3. 3

    Run

    Click on ▶️ Run button at the bottom of the page.

    This button only appears on desktop version (recommended). On browser, use 💾 Save button.

Explore This Guide​

  • 3 Privacy settings

Choose what to protect based on your needs:

Click any option to learn more about what it does.

Each change can be applied and reversed individually.

  • Some settings and commands may require technical knowledge to apply correctly.
  • Most users find the Normal protection above sufficient.

Remove "apport" package

The "apport" package is responsible for automatically generating crash reports for debugging. Apport software is provided using multiple packages such as "apport", "python3-apport", "apport-gtk", "apport-kde", among others. This script removes the main "apport" package that would lead other dependencies to be in orphaned states that can be auto-removed. It does not attempt to remove all packages in the suite as these can cause side effects and unintended crashes, such as deleting `python3-apport...

Disable Apport service

The Apport service can be stopped using the following command: "systemctl stop apport". Stopping the service can mitigate the risk of Ubuntu not respecting the opt-out configuration. This has happened before in different Ubuntu versions, as reported by the community. This script is used as part of a post-installation script by the National Cyber Security Centre in the UK.

Disable participation in Apport error messaging system

Opting out of Apport prevents it from creating crash files after a crash. It can be disabled by setting "enabled=0" in "/etc/default/apport". This setting comes enabled by default in a clean installation of Ubuntu and some of its derivatives (such as Pop!_OS). This script is used as part of a post-installation script by the National Cyber Security Centre in the UK.

Similar Guides​

Wider Goal​

Guides below includes this guide to achieve a wider goal.

See other more general settings that includes this one as one of its actions.

These plans combine multiple privacy settings, including this one, for stronger protection.

Ubuntu's error tracker explains crashes, hangs, and other severe errors to end users; lets them report an error; and collects these reports and shares them with Ub...
Visit category page

Same Goal​

Another guide in Disable Ubuntu error tracker 

See settings that are in the same category as this guide.

Using other actions in the same category may help you achieve your goal better.

Disable uploading errors (Whoopsie)

About the Creators​

These people have authored this documentation and written its scripts:

  • Avatar of undergroundwires. The creator of PrivacyLearn and privacy.sexy. Black and white portrait showing a person wearing a polka dot tie and suit jacket, reflecting the professional expertise behind the privacy protection tools.
    • Certified security professional
    • 7+ years experience securing banks
    • Open-source developer since 2005
    • EU advisor, Public Speaker, Moderator
    • Hundreds across the globe
    • Testers, reviewers, developers
    • Companies, military agencies
    • Community since 2017
About Us

Reviewed By​

This guide has undergone comprehensive auditing and peer review:

  • Expert review by undergroundwires​

    • Verified technical accuracy and editorial standards
    • Assessed system impact and user privacy risks

  • Public review by large community​

    • Privacy enthusiasts and professionals peer-reviewed
    • Millions of end-users tested across different environments

History​

We continually monitor our guides, their impact and all other privacy options. We update our guides when new information becomes available. On every update, we publicly store who made the change, what has been changed, why the change was made and when the change was made.

Review Change History Our Change Process