Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Apport review

Free#50 of 63 in Crash Reporting Software

A free, self-hosted Linux crash diagnostic component with deep debugging hooks.

3.7/10Editor score
Apport3.7 Visit Apport

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Apport is an open-source crash detection and reporting system maintained by Canonical. It is designed for developers and teams running Linux systems who need local collection of crash details rather than a hosted service. The component intercepts crashes from standard signals through the kernel coredump handler, captures unhandled Python exceptions, gathers operating-system debugging information, and stores reports locally. GTK, KDE, and command-line interfaces support different working environments, while package hooks add diagnostics specific to installed software.

Its strongest technical depth is post-mortem analysis. Apport can regenerate stack traces using debug symbols, helping turn a captured crash into information suitable for investigation. It also integrates with Linux package workflows through apt/dpkg and RPM backends, and it can submit standardized reports to Launchpad. These capabilities fit Ubuntu and other Linux distribution environments where package context, kernel crash handling, and bug-report workflows need to work together. The free, open-source model allows teams to deploy the component themselves across supported systems.

Apport is a focused Linux system component, not a cross-platform crash-reporting service. Teams operating Windows, macOS, or mixed fleets should choose a product that supports those platforms. Self-hosted deployment also means the organization is responsible for installing and maintaining the local component and its reporting workflow. Stack-trace regeneration is most useful when matching debug symbols are available, so teams should account for symbol management in their diagnostic process. Choose Apport when Linux-native collection, package-aware diagnostics, and Launchpad reporting are priorities; consider an alternative when you need a hosted console or broader platform coverage.

Apport pros and cons

  • Where it wins
    • Regenerates post-mortem stack traces with debug symbols
    • Captures crashes, Python exceptions and operating-system debugging data
    • Offers GTK, KDE and command-line interfaces with Launchpad submission
  • Where it doesn't
    • Runs on Linux only
    • Self-hosted deployment requires your team to operate the component
    • Stack-trace regeneration depends on available debug symbols

Apport fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update