Apport blob processing doesn't handle errors gracefully

[Graham Binns]

What happens:
If an error occurs during Apport blob processing, it just gets recorded in the log for the processing script. No OOPS is recorded and the user, who is left waiting for processing to complete, is never informed about the failure and it potentially left hanging forever (though we can assume that the need to eat will probably obviate this part of the bug).

What should happen:
We should record that the job failed to run (in fact, this is built into the Jobs system, so it shouldn't be hard to do). More importantly, we should tell the user that the job failed to run.

[Robert Collins (lifeless)]

If its logged at warning or above we'll get an OOPS.

[Robert Collins (lifeless)]

I've looked at the code, it doesn't log - it will just throw, and that will OOPS these days.