Comment 13 for bug 62511

As noted, SIGQUIT as a crashdump signal is not a bug in itself. It's also not a bug that SIGQUIT is handled by the crashdump helper (since it's designed to be invoked any time a core dump would occur). If apport wants to ignore this signal, that's great.

If the bug is that apport is too slow to ignore the signal (as the user is concerned about response time), then that's something that apport will have to be faster about, or the user will have to disable apport usage.