excepthook in gtk_ui.py should write a crash report instead of calling ubuntu-bug
Bug #901381 reported by
Brian Murray
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Fix Released
|
High
|
Brian Murray |
Bug Description
In ubiquity/
1) the bug is tagged apport-bug and not apport-crash
2) apport bug patterns are not checked
I discovered this when looking at bug 901330 which was reported after I wrote the bug pattern for bug 850264. I tested the bug pattern and it does in fact match bug 901330 and the pattern is live on people.
I think instead that the excepthook should create a crash report file in /var/crash which then be picked up by apport.
Related branches
lp:~brian-murray/ubiquity/bug-901381
- Ubuntu Installer Team: Pending requested
-
Diff: 39 lines (+9/-2)2 files modifieddebian/changelog (+6/-1)
ubiquity/frontend/gtk_ui.py (+3/-1)
tags: | added: patch |
To post a comment you must log in.
Is the appropriate notifier that sets an inotify on /var/crash actually running in ubiquity-dm mode though? I think that needs to happen too for this type of change to work.