Comment 13 for bug 599504

Well, I've been trying for months now to get apport to file a report when firefox crashes (or locks up). Here is a list of things that happen:

1) firefox crashes (or pulseaudio, or plugin container, etc) and apport asks if I want to file a report. Apport then responds saying it can not retrieve the error message, and does not support reporting in this situation

2) firefox crashes (or pulseaudio, or plugin container, etc) and apport asks if I want to file a report. Apport then responds saying my system is not up-to-date, and will not file a report. This is a real problem, because invariably there is some new system update that has come out in the [1,few] days since the last restart of firefox. 99% of the time the update looks completely unrelated to firefox crashing. This really, really needs to be able to be disabled.

3) Some insidious bug causes firefox to lock up and become unresponsive instead of outright segfaulting/etc. The firefox windows dim to show its hanging, the drive may be accessed for a while. But, eventually the drive access ceases, and firefox remains unresponsive with its windows dimmed apparently forever (I once waited more than 24hrs).

Its sad, but my system seems to be getting less stable with ubuntu updates, not more so.

And, damn it, I've lost the system beep. Yes, I know, I'll file a separate bug report.