Handle bugs in libraries better
Bug #1072854 reported by
Evan
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Errors |
Confirmed
|
High
|
Unassigned | ||
Bug Description
If a library is the root cause of a crash, then much of the data on the bucket pages is not helpful.
The graph is somewhat correct because it is based on the number of instances of the problem signature, so it shows the count for the bug in the library for this application's use of it. It obviously doesn't show the count for other applications using that library.
The package versions which have this issue, while technically accurate, is ultimately unhelpful. Any version of this package may potentially show the issue because it's occurring in the library below.
| Changed in errors: | |
| importance: | Undecided → High |
| status: | New → Confirmed |
Revision history for this message
| Matthew Paul Thomas (mpt) wrote | #2 |
To post a comment you must log in.
From the sprint discussion: This might be helped by the "What’s unusual about machines affected by this error". For example:
What’s unusual about machines affected by this error
libproxy 0.4.7-0ubuntu4.1 or earlier ... 9.6 % .... 0.0 %
libproxy 0.4.7-0ubuntu6 or later ...... 90.4 % .. 100.0 %