crash signature for Python Tracebacks can be too generic
Bug #1693040 reported by
Brian Murray
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Apport |
New
|
Undecided
|
Unassigned |
Bug Description
This bucket, https:/
/usr/bin/
However, in this case this is too generic as there have been two iterations of this specific crash.
One traceback ends with:
FileNotFoundError: [Errno 2] Aucun fichier ou dossier de ce type: 'gnome-
Another with:
FileNotFoundError: [Errno 2] Arquivo ou diretório não encontrado: '/usr/lib/
These are two separate issues and they should not be bucketed together.
To post a comment you must log in.
This signature is created in apport's report.py in the function crash_signature. The doc strings includes the following:
1274 For Python crashes, this concatenates the ExecutablePath, exception
1275 name, and Traceback function names, again separated by a colon.
Perhaps if the exception name includes "FileNotFoundError" we should include what the file is.