| 2013-02-08 14:39:35 |
Matthew Paul Thomas |
description |
We may giggle at Apport for saying that an application crashed "(now or in the past)", but it raises a valid point.
If whoopsie crashes or is killed, so that a subsequent crash log isn't dealt with until Ubuntu next restarts, it does not then make sense to put up the standard application crash alert inviting you to reopen an application that might not have been open for days.
We should design and implement a replacement for this alert. Maybe:
- the standard crash alert should still appear, but with custom text recognizing that the problem happened a while ago, and no Reopen function;
- the error should be grouped with whatever error happens next;
- the error shouldn't be reported at all. |
We may giggle at Apport for saying that an application crashed "(now or in the past)", but it raises a valid point.
If whoopsie crashes or is killed, so that a subsequent crash log isn't dealt with until Ubuntu next restarts, it does not then make sense to put up the standard application crash alert inviting you to reopen an application that might not have been open for days.
<https://wiki.ubuntu.com/ErrorTracker#error>: "Silent error types ... consist of: ... * Any error that occurs over a minute before the error alert could appear, where you have interacted with the session during that interval." |
|
