Python crashes are not limited to < 3 per day
Bug #603503 reported by
Sebastien Bacher
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Fix Released
|
Medium
|
Martin Pitt |
Bug Description
Binary package hint: apport
Using the current maverick version, new crash files for Python crashes don't have a CrashCount.
Changed in apport (Ubuntu): | |
importance: | Undecided → Low |
summary: |
- pops up for repeated crashes + pops up for repeated Python crashes |
summary: |
- pops up for repeated Python crashes + Python crashes are not limited to < 3 per day |
Changed in apport (Ubuntu): | |
assignee: | nobody → Martin Pitt (pitti) |
importance: | Low → Medium |
status: | New → Triaged |
description: | updated |
Changed in apport (Ubuntu): | |
status: | Triaged → In Progress |
Changed in apport (Ubuntu): | |
status: | In Progress → Triaged |
To post a comment you must log in.
example:
run gconf-editor, send it a sig11
$ grep CrashCount /var/crash/ _usr_bin_ gconf-editor. 1000.crash
$
run gconf-editor, send it a sig11
$ grep CrashCount /var/crash/ _usr_bin_ gconf-editor. 1000.crash
CrashCounter: 1
run gconf-editor, send it a sig11
$ grep CrashCount /var/crash/ _usr_bin_ gconf-editor. 1000.crash
CrashCounter: 1