[Bug 901381] Re: excepthook in gtk_ui.py should write a crash report instead of calling ubuntu-bug
Mario Limonciello
superm1 at ubuntu.com
Wed Dec 7 22:18:06 UTC 2011
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.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/901381
Title:
excepthook in gtk_ui.py should write a crash report instead of calling
ubuntu-bug
Status in “ubiquity” package in Ubuntu:
New
Bug description:
In ubiquity/frontend/gtk_ui.py apport-bug is called directly which
causes a couple of issues:
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.canonical.com.
I think instead that the excepthook should create a crash report file
in /var/crash which then be picked up by apport.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/901381/+subscriptions
More information about the foundations-bugs
mailing list