apport-bug exits with exit_success even if it fails

Status changed to 'Confirmed' because the bug affects multiple users.

Same is true for apport-cli.

Same is also tru for apport-kde, it exists with the following output on console:
QPainter::begin: Paint device returned engine == 0, type: 2
QPainter::end: Painter not active, aborted

and exit status (echo $?) is 1

When it will be fixed?
These programs don't want to submit bug and bug additional information for third-party packages (e.g. for ubuntu-tweak):
1) ubuntu-bug
2) apport-collect
3) apport-bug

$ lsb_release -rd
Description: Ubuntu 12.04.1 LTS
Release: 12.04

Mikhail: your problem has nothing to do with this report, and can be fixed only in the apps. Please refer to https://wiki.ubuntu.com/Apport/DeveloperHowTo foe additional info.

I've fixed it by exiting with exit code 1 from the "check_unreportable" function that displays the error dialog. See linked branch.

I'm not sure if it's a good idea though, because the function is supposed to check only, not abort the whole thing (isn't it?). I've tried returning false from the "run_report_bug" function that calls "check_unreportable" and then returning false from all the places that call "run_report_bug" but the error handling is still not advanced enough to pick up even those errors and bail out, so I guess I'll quit poking around and leave this to somebody who's familiar with the codebase.

I don't see an attached branch here, but indeed check_unreportable() should not exit the program. This needs to be passed down through the return values. Also, please keep in mind that /usr/share/apport/apport-gtk potentially process more than one report (and indeed this will happen a lot more often in the near future when we submit the "system level" reports in batches). So a single exit code does not tell you a lot.

Third party packages which want to integrate with Apport are much better off with shipping a proper package hook which adjusts the crash database.

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

This issue has sat incomplete for more than 60 days now. I'm going to close it as invalid. Please feel free re-open if this is still an issue for you. Thank you.