[Bug 1289580] Re: dist upgrade crash tracebacks include a tmpdir name

[Adam Conrad]

Hello Brian, or anyone else affected,

Accepted update-manager into precise-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/update-
manager/1:0.156.14.12 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: update-manager (Ubuntu Precise)
       Status: Triaged => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1289580

Title:
  dist upgrade crash tracebacks include a tmpdir name

Status in “ubuntu-release-upgrader” package in Ubuntu:
  Fix Released
Status in “update-manager” package in Ubuntu:
  Invalid
Status in “ubuntu-release-upgrader” source package in Precise:
  Invalid
Status in “update-manager” source package in Precise:
  Fix Committed
Status in “ubuntu-release-upgrader” source package in Saucy:
  Fix Released
Status in “update-manager” source package in Saucy:
  Invalid

Bug description:
  N.B. Before testing this bug ensure that python-apport is installed on
  Saucy.  See bug 1289604 for details.

  Test Case:
  1) run do-release-upgrade -d
  2) cancel the upgrade
  3) cd to /tmp/ubuntu-release-upgrader-XYZ/
  4) edit DistUpgrade/DistUpgradeController.py and put a division by zero error in the function askDistUpgrade (this is to make the release upgrader crash)
  5) sudo ./trusty --frontend=DistUpgradeViewGtk3
  6) Observe a system crash dialog and choose to report it
  7) Choose to view details of the crash report
  8) Observe a traceback with /tmp/ubuntu-release-upgrader-XYZ/ in it
  9) Do not submit the crash report

  With the packae from proprosed you'll see a DuplicateSignature field
  with XYZ replaced with tmpdir so /tmp/ubuntu-release-upgrader-tmpdir/

  
  Tracebacks from crashes in the release upgrader include a temporary directory name like so:

  Traceback (most recent call last):
    File "/tmp/ubuntu-release-upgrader-5gz_r8/trusty", line 10, in <module>
      sys.exit(main())
    File "/tmp/ubuntu-release-upgrader-5gz_r8/DistUpgrade/DistUpgradeMain.py", line 243, in main
      if app.run():

  Because the temporary directory name changes between systems and
  upgrade attempts duplicates are not often consolidated in the error
  tracker or in Launchpad.  Subsequently, it is difficult to judge the
  number of people affected by any particular crash in the release
  upgrade process.

  This should be fixed in the apport package hook for update-manager in
  Precise and ubuntu-release-upgrader in Saucy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1289580/+subscriptions