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

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 2.9.17

---------------
ubiquity (2.9.17) precise; urgency=low

  [ Colin Watson ]
  * Don't display "Ready when you are..." when the installer isn't actually
    waiting for user actions.
  * When waiting for user actions, just hide the progress bar and associated
    widgets rather than displaying "Ready when you are...", to avoid
    confusion associated with a progress bar being displayed when the system
    is in fact waiting for user input (LP: #670409, #925427).
  * Mark file descriptors used for communication with parted_server
    FD_CLOEXEC.
  * Restore finish-install's title after installing the oem-config frontend
    (LP: #925155).
  * Avoid duplicate call to osextras.find_on_path('check-language-support').
  * Stop filtering warnings from the apt module which are no longer emitted.
  * PEP-8 import ordering.
  * Make the "Choose a picture" page translatable (LP: #892384).
  * Make the "run all pending GTK events" function accessible from
    ubiquity.gtkwidgets, and use it in the test suite.  This makes the test
    suite about four seconds faster.
  * Fix sys.path mishandling in test suite.
  * Mark WPA2-only access points as secure.
  * Add initial tests for wireless page.
  * Automatic update of included source packages: choose-mirror 2.39ubuntu3,
    netcfg 1.68ubuntu11.

  [ Brian Murray ]
  * ubiquity/gtk_ui.py: in the crash handler also call apport directly if in
    the maybe-ubiquity mode (LP: #901381)
 -- Colin Watson <cjwatson at ubuntu.com>   Fri, 10 Feb 2012 17:27:15 +0000

** Changed in: ubiquity (Ubuntu)
       Status: In Progress => 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