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

[Martin Pitt]

Until a while ago, ubiquity did not call apport any more, so we rather
had the opposite problem of the apport GUI not appearing in only-
ubiquity mode. I fixed that recently, see bug 712677.

The current code calls

  self.previous_excepthook(exctype, excvalue, exctb)

which is the apport one if apport is installed. So I think this is fixed
now.

** Changed in: ubiquity (Ubuntu)
       Status: Triaged => Fix Released

-- 
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:
  Fix Released

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