I want to let Apport catching all crashes - system wide - which means also crashes in programs which are located for example inside the HOME folder of a user and not part of Ubuntu packages. Is there any configuration option to realize this?

Silly example:

#include <stdio.h>
int main() { printf("%n%n%n"); return 0; }

make test && ./test

Will create a crash but Apport will not intercept it.

CrashReporter on MacOS is able to create a crash report for all executable files regardless of where they are located in the system.

  • I did not mention anything about sending data. AFAIK Apport is not sending data, that's done by Whoopsie. I am personally only interested in having a .crash report on disk of a program which crashed in my HOME directory.
    – calquin
    Jan 24, 2013 at 10:08
  • Yes, once a crash appears in the app, I see either "executable does not belong to a package, ignoring" or nothing in /var/log/apport.log (Perhaps because of SIGABRT - I think those exceptions are not getting logged in general).
    – calquin
    Jan 24, 2013 at 10:39
  • When that comes up, is there a .crash file in /var/crash? If not, try checking before dismissing the dialog that says the but cannot be reported. If the .crash file is there, is there a problem using these tools (such as apport-unpack) to access the data in the file? Jan 24, 2013 at 10:49
  • No .crash in /var/crash, and also no dialog. I have edited the question. If you like to test, try to compile and run the snippet. (Ignore the compile warnings.)
    – calquin
    Jan 24, 2013 at 10:52

1 Answer 1


I couldn't find anything in the documentation, but from reading the code I saw that you can enable crash reports for unpackaged binaries by creating a file called ~/.config/apport/settings with the content:

  • This worked perfectly. It's the answer. I used ':' instead of '=', though but I guess '=' could work, too.
    – simich
    Jun 23, 2016 at 9:11

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .