[Bug 901381] Re: excepthook in gtk_ui.py should write a crash report instead of calling ubuntu-bug

[Martin Pitt]

@Brian: Yes, I think that makes sense. I think it should either re-raise
the exception and let /usr/share/pyshared/apport_python_hook.py do its
magic, or if that is inappropriate, import that module and call
apport_excepthook() directly.

@Mario: that problem is bug 712677, it's on my list of things to look
into for precise.

-- 
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