Confusing handling of crashes long after they happened
Bug #1018117 reported by
Matthew Paul Thomas
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Apport |
Triaged
|
Medium
|
Unassigned | ||
Bug 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.
<https:/
| Changed in apport: | |
| assignee: | nobody → Matthew Paul Thomas (mpt) |
Revision history for this message
| Martin Pitt (pitti) wrote | #1 |
| tags: | added: whoopsie-daisy |
| Changed in apport: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in apport: | |
| status: | Triaged → In Progress |
Revision history for this message
| Matthew Paul Thomas (mpt) wrote | #2 |
| Changed in apport: | |
| status: | In Progress → Triaged |
| assignee: | Matthew Paul Thomas (mpt) → nobody |
| description: | updated |
| summary: |
- No design for crashes handled long after they happened + Confusing handling of crashes long after they happened |
| tags: | added: rls-cc-incoming |
To post a comment you must log in.
FWIW, I'm fine with ignoring old errors. I don't think that crash reports are so precious that we need to bother the user about very old ones, we get plenty of them. This sounds similar (dup?) to bug 1033932.